Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]

[Eric Botcazou]

> Can you tell me if this stil happens with current CVS sources? Also,
> does libstdc++ build?

This is still present as of today (Thu Oct  9 04:48:45 UTC 2003) on Solaris 
2.6, 2.7, 2.8, 2.9 but not 2.5.1.

Here is for example a GDB session for:
FAIL: g++.dg/expr/enum1.C execution test

Program received signal SIGSEGV, Segmentation fault.
__atomic_add(int volatile*, int) (__mem=0x0, __val=1)
    at 
/opt/build/eric/gcc/sparc-sun-solaris2.8/libstdc++-v3/include/sparc-sun-solaris2.8/bits/atomicity.h:122
122       *__mem += __val;
(gdb) where
#0  __atomic_add(int volatile*, int) (__mem=0x0, __val=1)
    at 
/opt/build/eric/gcc/sparc-sun-solaris2.8/libstdc++-v3/include/sparc-sun-solaris2.8/bits/atomicity.h:122
#1  0xff2e3678 in std::ios_base::Init::Init() (this=0xff35b95c)
    at 
/opt/build/eric/gcc/sparc-sun-solaris2.8/libstdc++-v3/include/streambuf:437
#2  0xff2e16a0 in __static_initialization_and_destruction_0(int, int) (
    __initialize_p=-13256356, __priority=0)
    at 
/opt/build/eric/gcc/sparc-sun-solaris2.8/libstdc++-v3/include/iostream:77
(gdb)

Everything is fine on Thu Oct  2 03:49:53 UTC 2003.

-- 
Eric Botcazou