--- Comment #2 from pinskia at gcc dot gnu dot org 2006-05-05 17:33 ---
Interesting it does not fail on x86-linux-gnu
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27448
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-05-05 17:35 ---
Or this was just fixed yesterday. Can you give the output of gcc -v?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27448
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-05-05 17:38 ---
Also as of today this works on x86_64 also.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27448
--- Comment #5 from ak at muc dot de 2006-05-05 18:13 ---
I got a new gcc today before reporting
/pkg/gcc-4.2/bin/gcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc/configure --prefix=/pkg/gcc-4.2-060409
--disable-checking --enable-languages=c,c++
--- Comment #6 from ak at muc dot de 2006-05-05 18:14 ---
Oops as you can see I indeed used an old gcc by mistake - a symlink
was set wrong. With the current gcc it works.
--
ak at muc dot de changed:
What|Removed |Added
