For developer scenarios, linking takes the lion’s share of the application’s build time. From our investigation we know that the Visual C++ linker spends a large fraction of its time in preparing, merging and finally writing out debug information. This is especially true for non-Whole Program Optimization scenarios.
The time spent in the link phase could be a significant portion of an applications overall build time for most large projects. A user can quickly determine this by adding the ‘/time’ flag to the linker command line. The ‘Final: Total time’
If you guys follow Jason Zander’s (Visual Studio corporate Vice President) blog, you learned two days ago that the Visual Studio 2010 Service Pack 1 whose Beta had been released last December achieved final release stage. Today is generally available (last Tuesday was only for MSDN subscribers).
We know that build throughput for applications are a time crunch on developer productivity. We have spent some time on improving linker throughput and other areas in VS2010, and will continue to investigate improving overall build throughput in future releases.
In this blog post,
Hello, my name is Chandler Shen, a developer from the Visual C++ Shanghai team.
We have made some changes in the upcoming Visual C++ 2010 release to improve the performance of linker. I would like to first give a brief overview of the linker and how we analyze the bottlenecks of current implementation.
Hello, my name is Chandler Shen, a developer from Visual C++ Shanghai team.
There is some confusion about warning LNK4221 and whether it is safe to ignore it. I would like to give an explanation on when you may encounter this warning and provide tips for some typical scenarios and workarounds.