Recognize more cases where we can use a 32-bit move instead of a 64-bit move.

Recognize more cases where we can emit 32-bit instruction for 64-bit immediate constants.

Combine successive constant stores to one store.

Enable tail merge optimizations with the presence of C++ EH or Windows SEH (see here and here for EH or SEH).

RBP-relative address mode is one byte shorter than RSP-relative.

More aggressively use RBP as the frame pointer to access local variables.

Some of the improvements are listed below: In VS2010, several effective optimizations are introduced or improved for X64 architecture. With that the scenario (PGI) runs are about 1.7X faster.Ĭode size reduction for X64 target: Code size is a crucial factor to performance especially for applications that are performance-sensitive to the behavior of instruction cache or working set. In VS2010, we s upport a no-lock version of the instrumented binaries.

One major drawback of PGO is that the instrumented run is usually several times slower than a regular optimized run. See here or here for an introduction of PGO. text size greater than 50MB) is sped up by ~30%.įaster Pogo Instrumentation run: Profile Guided Optimization (PGO) is an approach to optimization where the compiler uses profile information to make better optimization decisions for the program. An LTCG build of Microsoft SQL Server (an application with. In VS2010, we improved the information merging process and sped up LTCG compilation significantly. To merge information from all modules, LTCG compilation generally takes longer than non-LTCG compilation, particularly for large applications. Today, I’m going to introduce some noteworthy improvements in Visual Studio 2010.įaster LTCG Compilation: LTCG (Link Time Code Generation) allows the compiler to perform better optimizations with information on all modules in the program (for more details see here ).

Hello, I’m Ten Tzen, a Compiler Architect on the Visual C++ Compiler Code Generation team.

Microsoft visual studio code 2010