------- Comment #9 from bkoz at gcc dot gnu dot org 2006-02-22 17:26 -------
HP, I also don't know what is going on here, but it seems unlikely that the libstdc++ code is to blame, just because there's been no change to this part of libstdc++ in quite a while. One thing you could check, if you have various compilers for cris around, is to try to compile newer libstdc++ sources with a known good cris compiler. That would at least let you know where things are problematic, without digging too far into this. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25815
