GCC 3.3

[Eric Botcazou]

> If there is some incredibly vital patch, it can go in to the next
> prerelease, but things like "glibc really wants this" aren't going to
> make it in that round.

Sorry for arriving so late in the game but, as the machines at stake are not 
exactly fast, I was previously concentrating on the 3.2.3 release and then 
left for two weeks...

The bad news: we have a bunch of C++ regressions on sparc-sun-solaris2.5.1

3.3pre: http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00337.html
3.2.3pre: http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00894.html

and sparc-sun-solaris2.6

3.3pre: http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00338.html
3.2.3pre: http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00894.html

(sparc-sun-solaris2.[7-9] are clean).

The good news: they appear to have the same origin (in libstdc++-v3), see the 
attached log file.

I'm going to try to debug them but, as I'm not an expert of libstdc++-v3 at 
all, any help would be *greatly* appreciated (emphasis by me :-).

-- 
Eric Botcazou
-------------- next part --------------
A non-text attachment was scrubbed...
Name: solaris2.6-c++bug.log
Type: text/x-log
Size: 13418 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20030506/d28b0773/attachment.bin>