Stefan Krah added the comment: "I ran a quick test with profile-guided optimization (PGO, pronounced "pogo"), which has supposedly been improved since VC9, and +saw a very unscientific 20% speed improvement on pybench.py and 10% size reduction in python35.dll. I'm not sure what we used +to get from VC9, but it certainly seems worth enabling provided it doesn't break anything. (Interestingly, PGO decided that +only 1% of functions needed to be compiled for speed. Not sure if I can find out which ones those are but if anyone's +interested I can give it a shot?)"
Steve, could you try if this is still a problem? The (presumed) Visual Studio bug only surfaced when training the instrumented build with "profiletests.txt" and then doing the PGupdate build. I'm opening this issue again and leave it at release blocker for 3.5. ---------- nosy: +steve.dower status: closed -> open type: -> compile error versions: +Python 3.5 -Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15993> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
