STINNER Victor <[email protected]> added the comment:
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.
----------
title: llvm-gcc-4.2 miscompiles Python (XCode 4.1+ on Mac OS 10.7) ->
llvm-gcc-4.2 miscompiles Python (XCode 4.1 on Mac OS 10.7)
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue13241>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
