2011/10/28 Aaron Patterson <tenderlove / ruby-lang.org>:
> On Thu, Oct 27, 2011 at 10:46:10AM +0900, nagachika wrote:
>> Which compiler did you use to build ruby?
>
> [aaron@higgins ruby (08b3d47...)]$ gcc -v
> Using built-in specs.
> Target: i686-apple-darwin11
> Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/src/conf=
igure --disable-checking --enable-werror --prefix=3D/Developer/usr/llvm-gcc=
-4.2 --mandir=3D/share/man --enable-languages=3Dc,objc,c++,obj-c++ --progra=
m-prefix=3Dllvm- --program-transform-name=3D/^[cg][^.-]*$/s/$/-4.2/ --with-=
slibdir=3D/usr/lib --build=3Di686-apple-darwin11 --enable-llvm=3D/private/v=
ar/tmp/llvmgcc42/llvmgcc42-2335.15~25/dst-llvmCore/Developer/usr/local --pr=
ogram-prefix=3Di686-apple-darwin11- --host=3Dx86_64-apple-darwin11 --target=
=3Di686-apple-darwin11 --with-gxx-include-dir=3D/usr/include/c++/4.2.1
> Thread model: posix
> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00=
)
>
>> Though I can't reproduce in my environment, I guess it is related to
>> deleted workaround for llvm at r33408.
>> Could you try with reverting r33408?
>
> The problem started happening at revision r33419. =A0However, if I revert
> r33408, everything works again. :(
>
> I will revert r33408 and commit.

llvm-gcc is not supported because it is too buggy and no future.
(This is the last release to support the llvm-gcc frontend
 http://llvm.org/releases/2.9/docs/ReleaseNotes.html#additionalinfo )
Please use GNU GCC or try LLVM/Clang.

Anyway in my experience, LLVM has some over optimization problem.
So ruby needs some hacks like r33408 or r32201.

--=20
NARUSE, Yui =A0<naruse / airemix.jp>