Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx> writes: > > > > Is this issue fixed with gcc 4.1.2? If so, is there a bugzilla entry > > > > for that? > > > > > Maybe http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27236 > > > > I did a rebuild with -fno-unit-at-a-time, which still created the same > > problematic asm, so I think it's another issue. > > Have you got a test case? My current test case is to build Linux Kernel 2.6.16.43/2.6.16.52, distro is SuSE SLES10. $ gcc -v Using built-in specs. Target: i586-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.0 --enable-ssp --disable-libssp --enable-java-awt=gtk --enable-gtk-cairo --disable-libjava-multilib --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --without-system-libunwind --with-cpu=generic --host=i586-suse-linux Thread model: posix gcc version 4.1.0 (SUSE Linux) My next check is to see whether this is SuSE specific or not. If not i'll provide a smaller testcase.c ASAP. /holger
