http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56068
--- Comment #15 from Jason Pyeron <jpyeron at pdinc dot us> 2013-01-21 20:14:10 UTC --- (In reply to comment #12) > (In reply to comment #11) > > I will try 4.6 to prove that. Off to build 4.6... > ... > If that prints 0 for OSXSAVE and non-zero for AVX then it's the same problem I > had. > Maybe GCC could work around it by checking both flags in the AVX detection > logic. mockbuild@centos6-64bit-builder ~/build/BUILD/gcc/test (mock-chroot) $ gcc test.c -march=native mockbuild@centos6-64bit-builder ~/build/BUILD/gcc/test (mock-chroot) $ ./a.out bit_OSXSAVE (134217728) = 0 bit_AVX (268435456) = 0 mockbuild@centos6-64bit-builder ~/build/BUILD/gcc/test (mock-chroot) $ gcc test.c mockbuild@centos6-64bit-builder ~/build/BUILD/gcc/test (mock-chroot) $ ./a.out bit_OSXSAVE (134217728) = 0 bit_AVX (268435456) = 0 on the other note, I am currently building svn://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch
