This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients Sjlver, brett.cannon, koobs, ned.deily, ronaldoussoren, vstinner
Date 2014-04-01.22:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Just as an experiment (using the 3.4 branch and the Xcode 5.1 clang), the list of unique symbols not found during the test dlopen in when using -flto:


Anyone see a pattern there? 

Do we know if anyone has tried to use LTO with a Python build previously?  I've never tried it myself and there certainly could be ld and/or dyld differences on OS X.  Also, some thought would need to go into and tests developed to see what the performance trade-offs are.  For example, I could imagine that LTO might be have more impact if the standard library extension modules were statically linked, e.g. via Modules/Setup*.  And there are at least three separate current build configurations to consider on OS X: unshared, --enable-shared, --enable-framework.  One would need to look at things like what effect these all have on memory and shared memory footprints as well as cpu resources and real time, with and without LTO and/or other optimizations.  It certainly would be an interesting project for someone with the interest and time.

Potentially supporting LTO seems to me to be more of a feature than a bug so I think should be considered a 3.5 issue, at least initially.
Date User Action Args
2014-04-01 22:33:52ned.deilysetrecipients: + ned.deily, brett.cannon, ronaldoussoren, vstinner, koobs, Sjlver
2014-04-01 22:33:52ned.deilysetmessageid: <>
2014-04-01 22:33:52ned.deilylinkissue21122 messages
2014-04-01 22:33:51ned.deilycreate