Congratulations, you have found a GCC bug. Run the compilation by hand
with -v -save-temps, and then take the -v output and the .i file and
include them in your bug report to the GCC folks.
Note that I tried Red Hat 7's version of gcc-2.96 and it also crashed on
some of the Hurd sources (though not that file, and none of the crash I saw
looked like that one). When I went from -O3 to -O2 (-O3 turns on lots of
inlining), it stopped crashing. This level of optimization dealing with
heavy inlining (we have lots of inlinable functions in the Hurd code) seems
to be a moving target in recent GCC versions.
If you want to pursue this, you should probably get a recent development
snapshot of GCC and see if that crashes using -O3.
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
