"Joe Smith" <unknown_kev_cat at hotmail.com> wrote in message news:ea1i1e$l5c$1 at sea.gmane.org... > > "Neil Hodgson" <nyamatongwe at gmail.com> wrote in message > news:50862ebd0607232003gc800a48r3853bd773d3a7f21 at mail.gmail.com... >> Trent Nelson: >> >>> I ended up playing around with Profile Guided Optimization, running >>> ``python.exe pystones.py'' to collect call-graph data after >>> python.exe/Python24.dll had been instrumented, then recompiling with the >>> optimizations fed back in. >> >> It'd be an idea to build a larger body of Python code to run the >> profiling pass on so it doesn't just optimize the sort of code in >> pystone which is not very representative. Could run the test suite as >> it would have good coverage but would hit exceptional cases too >> heavily. Other compilers (Intel?) support profile directed >> optimization so would also benefit from such a body of code. >> > > GCC suppost profiling optimized code. Err... That was supposed to say "supports profile-optimized code". The rest of the message was indeed about Profile Guided Optimization in gcc.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4