PR 8146

Nathanael Nerode
Wed Nov 6 10:13:00 GMT 2002

This seems like it is probably a bug with the i686-specific code production 
in gcc 3.2, as opposed to the i386 generic code production; see and

Sending this message to keep a paper trail in the bug report.

More information about the Gcc-bugs mailing list