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 vstinner
Recipients Oleg.Plakhotnyuk, ezio.melotti, ned.deily, vstinner
Date 2011-10-26.11:52:50
SpamBayes Score 7.5539575e-13
Marked as misclassified No
Message-id <1319629971.1.0.114339840689.issue13241@psf.upfronthosting.co.za>
In-reply-to
Content
I asked for more information about llvm-gcc on IRC (#llvm). Extracts:

 - "llvm-gcc is not maintained." ("Clang and DragonEgg are.) "Apple is the maintainer of Apple's version of llvm-gcc and clang."
 - "Apple ships a [llvm-gcc] branch at a random point in svn + some bug fixes, not a proper release."
 - "llvm-gcc is Apple's GCC (which was never sync'd with mainline past 4.2.1 because the FSF changed the license) with LLVM on the back end."
 - llvm-gcc-4.5 in Ubuntu 10.10 is not llvm-gcc, it's dragonegg, a new project

If I understood correctly, llvm-gcc is only the default C compiler of Xcode 4.1. I don't think that you should workaround llvm-gcc bugs. If you are using Xcode 4.1, you can compile Python with clang. clang is a different C compiler and it doesn't have the bug.
History
Date User Action Args
2011-10-26 11:52:51vstinnersetrecipients: + vstinner, ned.deily, ezio.melotti, Oleg.Plakhotnyuk
2011-10-26 11:52:51vstinnersetmessageid: <1319629971.1.0.114339840689.issue13241@psf.upfronthosting.co.za>
2011-10-26 11:52:50vstinnerlinkissue13241 messages
2011-10-26 11:52:50vstinnercreate