Bootstrap failure on irix6.5 possibly caused by new C++ parser?

["Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>]

Mark,

I'm getting a new bootstrap failure on mips-sgi-irix6.5 today on the
trunk.  It occurs after the 3-stage when building libstdc++-v3:

 > /caip/u58/ghazi/gcc-testing/build/gcc/xgcc -shared-libgcc
 >   -B/caip/u58/ghazi/gcc-testing/build/gcc/ -nostdinc++
 >   -L/caip/u58/ghazi/gcc-testing/build/mips-sgi-irix6.5/libstdc++-v3/src
 >   -L/caip/u58/ghazi/gcc-testing/build/mips-sgi-irix6.5/libstdc++-v3/src/.libs
 >   -B/usr/local/mips-sgi-irix6.5/bin/ -B/usr/local/mips-sgi-irix6.5/lib/
 >   -isystem /usr/local/mips-sgi-irix6.5/include -nostdinc++
 >   -I/caip/u58/ghazi/gcc-testing/build/mips-sgi-irix6.5/libstdc++-v3/include/mips-sgi-irix6.5
 >   -I/caip/u58/ghazi/gcc-testing/build/mips-sgi-irix6.5/libstdc++-v3/include
 >   -I../../../../egcc-CVS20021228/libstdc++-v3/libsupc++
 >   -I../../../../egcc-CVS20021228/libstdc++-v3/libmath -g -O2
 >   -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline
 >   -fdiagnostics-show-location=once -ffunction-sections -fdata-sections
 >   -c ../../../../egcc-CVS20021228/libstdc++-v3/src/codecvt.cc -DPIC -o
 >   .libs/codecvt.o
 > ../../../../egcc-CVS20021228/libstdc++-v3/src/codecvt.cc: In member function `
 >    virtual int std::codecvt<char, char, mbstate_t>::do_encoding() const':
 > ../../../../egcc-CVS20021228/libstdc++-v3/src/codecvt.cc:100: internal compiler error: RTL
 >    flag check: RTX_INTEGRATED_P used with unexpected rtx code `UnKnown' in
 >    priority, at haifa-sched.c:808
 > Please submit a full bug report,
 > with preprocessed source if appropriate.
 > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 > make[4]: *** [codecvt.lo] Error 1


The annoying part is that the failure goes away if I add --save-temps,
so I assume it's not possible to provide a .ii file that reproduces
the crash in a cross compiler. :-(  If you still think it would be
useful to provide it let me know.

Bootstrap previously succeeded on 12/26 for irix6.2, as shown here:
http://gcc.gnu.org/ml/gcc-testresults/2002-12/msg01174.html and for
irix6.5 a couple of days before that.  So I think it's possible or
perhaps even likely that this was caused by the new parser.

		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu