"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. One caveat is that the profile-enabled builds ause a GPL'd library. Not a problem for Python right now as it is GPL-compatible, but a caveat non-the-less. That does not apply to the final optimized app. Anyway the flags used are: "-fprofile-generate" and "-fprofile-use".
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