Visual Studio 2013 Update 2 includes a number of fixes filed through Connect:
Thanks to everyone who provided feedback!
Any word on loop-interchange optimization and loop-hoisting optimization: stackoverflow.com/.../11227809 ? If you venture a guess, do you see it coming in this century?
I think there are enormous commonalities which can be considered for all these programming platforms. Loop-interchange and loop-invariant hoisting being the top of the list..
Cool, thanks! I think _thats_ what the community was expecting for a long time as part of the release notes - a comprehensive list of bugfixes! As opposed to "Update 2: Some C++ compiler crashes and language conformance issues have been addressed." PLEASE! do continue that for all future updates and service packs of VS. We are all developers, not offices users, we can handle such a list, we want such a list!
Agreed, that's a fine move, Eric.
Nice to see so many variadic template compiler-related issues resolved.
Thank's for sharing this with us :-)
It's good to see that my bug is fixed too ;-) (806758, unlisted above, but perhaps it's a duplicate)
Thank you very much for the detailed list! Wow, there are some bugfixes I didn't expect in a VC12 update.
Thanks, Eric! Does Visual Studio 2013 Update 2 also include the bug fix of "Initializer lists leaking memory", connect.microsoft.com/.../807419 ? It seems so, as I cannot reproduce that memory leak anymore, while I could with Update 1.
@Niels, yes it does!
@Super Mario: I'm on the CLR team and am the owner of .NET Native. Yes, the C++ compiler team absolutely shares their secret recipes with .NET. In fact, .NET Native uses the C++ optimizer (N-UTC) to create our binaries.
@Andrew Pardoe [MSFT],
I am so glad to know that! Thanks for sharing with us. Please share your thoughts on Loop-interchange and loop-invariant hoisting optimizations and how compiler optimization guys are planning to go about them. I have read some material available online on this subject and few clues about how Intel compiler guys have managed to implement it.
The question I referred to is the top question on SO community. Masses will be queuing to learn about your progress in that dimension.
Unfortunately, after all these effort Internet Explorer lags (at least 500 times behind Chrome, Safari and Firefox) in DOM manipulation test written in 2003 by one of the Google employee: http://jsfiddle.net/XPqdS/ (button press) and http://jsfiddle.net/LQMdC/ (on document load). They are extremely basic code structs (and common in all mustache family languages). But apparently IE are still acting on fair-enough strategy rather than aggressively and greedily eking out performance advantages with new explorations; be it a millisecond of performance gain, its still a gain. If others can do it in 10 ms or so, we would expect MSFT product to calculate in less than 10 ms (given all the experience and brilliance you guys have)! But here we are at >1200ms mark.
Template specialization on variadic function arguments can cause internal compiler errors. (link)
Variadic templates can cause internal compiler errors.
These seem to be not entirely fixed, I raised a bug report some months ago. Code works fine on gcc. (827051)