* Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
@ 2003-10-03 14:23 Bradley Lucier
2003-10-03 14:51 ` Eric Botcazou
2003-10-10 20:35 ` Bradley Lucier
0 siblings, 2 replies; 18+ messages in thread
From: Bradley Lucier @ 2003-10-03 14:23 UTC (permalink / raw)
To: gcc, libstdc++; +Cc: Bradley Lucier
Just a note that there were several thousand g++ and libstdc++ test
failures on 3.4 mainline from yesterday afternoon on sparc and sparc64;
full test results are at
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00119.html
Brad
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 14:23 Heads up: Several thousand g++ and libstdc++ test failures on sparc[64] Bradley Lucier
@ 2003-10-03 14:51 ` Eric Botcazou
2003-10-03 15:41 ` Benjamin Kosnik
2003-10-03 15:42 ` Bradley Lucier
2003-10-10 20:35 ` Bradley Lucier
1 sibling, 2 replies; 18+ messages in thread
From: Eric Botcazou @ 2003-10-03 14:51 UTC (permalink / raw)
To: Bradley Lucier; +Cc: gcc, libstdc++
> Just a note that there were several thousand g++ and libstdc++ test
> failures on 3.4 mainline from yesterday afternoon on sparc and sparc64;
> full test results are at
>
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00119.html
Everything was as usual just hours before:
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00117.html
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00116.html
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00115.html
--
Eric Botcazou
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 14:51 ` Eric Botcazou
@ 2003-10-03 15:41 ` Benjamin Kosnik
2003-10-03 16:00 ` Andreas Tobler
` (2 more replies)
2003-10-03 15:42 ` Bradley Lucier
1 sibling, 3 replies; 18+ messages in thread
From: Benjamin Kosnik @ 2003-10-03 15:41 UTC (permalink / raw)
To: Eric Botcazou; +Cc: lucier, gcc, libstdc++
Can you tell me if this stil happens with current CVS sources? Also,
does libstdc++ build?
thanks,
benjamin
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 14:51 ` Eric Botcazou
2003-10-03 15:41 ` Benjamin Kosnik
@ 2003-10-03 15:42 ` Bradley Lucier
1 sibling, 0 replies; 18+ messages in thread
From: Bradley Lucier @ 2003-10-03 15:42 UTC (permalink / raw)
To: Eric Botcazou; +Cc: Bradley Lucier, gcc, libstdc++
On Friday, October 3, 2003, at 09:53 AM, Eric Botcazou wrote:
>> Just a note that there were several thousand g++ and libstdc++ test
>> failures on 3.4 mainline from yesterday afternoon on sparc and
>> sparc64;
>> full test results are at
>>
>> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00119.html
>
> Everything was as usual just hours before:
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00117.html
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00116.html
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00115.html
You updated a few hours later (I should have given the update time in
GMT); I'll try it again now. Expect esults in about 14 1/2 hours :-(.
Thanks.
Brad
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 15:41 ` Benjamin Kosnik
@ 2003-10-03 16:00 ` Andreas Tobler
2003-10-03 17:59 ` Gabriel Dos Reis
2003-10-04 3:56 ` Bradley Lucier
2003-10-09 16:04 ` Eric Botcazou
2 siblings, 1 reply; 18+ messages in thread
From: Andreas Tobler @ 2003-10-03 16:00 UTC (permalink / raw)
To: Benjamin Kosnik; +Cc: gcc, libstdc++
Benjamin Kosnik wrote:
> Can you tell me if this stil happens with current CVS sources? Also,
> does libstdc++ build?
I started a build this morning on darwin, linuxppc, sol9 and hppa-linux.
Darwin, linuxppc are ok. Sol9 and hppa suffer these failures. Now I
synced libstdc++ again on sol9 and build. I think results will be
available in a few minutes. But I'd say it will be the same. And yes,
libstdc++ will build.
Affected are g++, libstdc++ and I think also libgcj?
Andreas,
BTW, Benjamin, for further details #gcc irc.oftc.net
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 16:00 ` Andreas Tobler
@ 2003-10-03 17:59 ` Gabriel Dos Reis
2003-10-03 18:03 ` Andreas Tobler
0 siblings, 1 reply; 18+ messages in thread
From: Gabriel Dos Reis @ 2003-10-03 17:59 UTC (permalink / raw)
To: Andreas Tobler; +Cc: Benjamin Kosnik, gcc, libstdc++
Andreas Tobler <toa@pop.agri.ch> writes:
| BTW, Benjamin, for further details #gcc irc.oftc.net
I would be highly desirable if discussions on such details about
GCC and its components happened on GCC lists so that they can be
archived for future references.
-- Gaby
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 17:59 ` Gabriel Dos Reis
@ 2003-10-03 18:03 ` Andreas Tobler
2003-10-03 21:32 ` Zack Weinberg
0 siblings, 1 reply; 18+ messages in thread
From: Andreas Tobler @ 2003-10-03 18:03 UTC (permalink / raw)
To: Gabriel Dos Reis; +Cc: Benjamin Kosnik, gcc, libstdc++
Gabriel Dos Reis wrote:
> Andreas Tobler <toa@pop.agri.ch> writes:
>
> | BTW, Benjamin, for further details #gcc irc.oftc.net
>
> I would be highly desirable if discussions on such details about
> GCC and its components happened on GCC lists so that they can be
> archived for future references.
No worry, I certainly will post my investigations on the LISTS. At the
moment I binary search the offending patch which introduced the
failures. As it seems it is a libstdc++-v3 issue and not a front end
thingy. It takes a few minutes until I have it.
Sorry for mentioning irc. Just thought for faster tracking the failure
some online hints would help.
Andreas
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 18:03 ` Andreas Tobler
@ 2003-10-03 21:32 ` Zack Weinberg
2003-10-03 21:47 ` Gabriel Dos Reis
0 siblings, 1 reply; 18+ messages in thread
From: Zack Weinberg @ 2003-10-03 21:32 UTC (permalink / raw)
To: Andreas Tobler; +Cc: Gabriel Dos Reis, Benjamin Kosnik, gcc, libstdc++
Andreas Tobler <toa@pop.agri.ch> writes:
>
> Sorry for mentioning irc. Just thought for faster tracking the failure
> some online hints would help.
I don't think anyone should apologize for mentioning irc. The channel
has been a valuable resource for quick communication between
developers, and its use should be encouraged.
However, perhaps it would be a good idea to have logs of channel
traffic posted somewhere. Other free-software projects that use
IRC for developer discussion do this.
zw
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 21:32 ` Zack Weinberg
@ 2003-10-03 21:47 ` Gabriel Dos Reis
0 siblings, 0 replies; 18+ messages in thread
From: Gabriel Dos Reis @ 2003-10-03 21:47 UTC (permalink / raw)
To: Zack Weinberg; +Cc: Andreas Tobler, Benjamin Kosnik, gcc, libstdc++
"Zack Weinberg" <zack@codesourcery.com> writes:
| Andreas Tobler <toa@pop.agri.ch> writes:
|
| >
| > Sorry for mentioning irc. Just thought for faster tracking the failure
| > some online hints would help.
|
| I don't think anyone should apologize for mentioning irc. The channel
| has been a valuable resource for quick communication between
| developers, and its use should be encouraged.
FWIW, nobody has been discouraging use of IRC for communication
between developpers. My remark was very specific.
-- Gaby
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 15:41 ` Benjamin Kosnik
2003-10-03 16:00 ` Andreas Tobler
@ 2003-10-04 3:56 ` Bradley Lucier
2003-10-09 16:04 ` Eric Botcazou
2 siblings, 0 replies; 18+ messages in thread
From: Bradley Lucier @ 2003-10-04 3:56 UTC (permalink / raw)
To: Benjamin Kosnik; +Cc: Bradley Lucier, Eric Botcazou, gcc, libstdc++
On Friday, October 3, 2003, at 10:40 AM, Benjamin Kosnik wrote:
> Can you tell me if this stil happens with current CVS sources?
Yes
> Also, does libstdc++ build?
Yes. Final results in a few hours.
Brad
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 15:41 ` Benjamin Kosnik
2003-10-03 16:00 ` Andreas Tobler
2003-10-04 3:56 ` Bradley Lucier
@ 2003-10-09 16:04 ` Eric Botcazou
2 siblings, 0 replies; 18+ messages in thread
From: Eric Botcazou @ 2003-10-09 16:04 UTC (permalink / raw)
To: Benjamin Kosnik; +Cc: lucier, gcc, libstdc++
> 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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-03 14:23 Heads up: Several thousand g++ and libstdc++ test failures on sparc[64] Bradley Lucier
2003-10-03 14:51 ` Eric Botcazou
@ 2003-10-10 20:35 ` Bradley Lucier
2003-10-11 6:38 ` Eric Botcazou
1 sibling, 1 reply; 18+ messages in thread
From: Bradley Lucier @ 2003-10-10 20:35 UTC (permalink / raw)
To: Bradley Lucier; +Cc: gcc, libstdc++
It seems that the g++ errors disappeared yesterday, but many of the
libstdc++ ones remain:
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00446.html
Brad
On Friday, October 3, 2003, at 09:22 AM, Bradley Lucier wrote:
> Just a note that there were several thousand g++ and libstdc++ test
> failures on 3.4 mainline from yesterday afternoon on sparc and
> sparc64; full test results are at
>
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00119.html
>
> Brad
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-10 20:35 ` Bradley Lucier
@ 2003-10-11 6:38 ` Eric Botcazou
2003-10-11 6:44 ` Andreas Tobler
0 siblings, 1 reply; 18+ messages in thread
From: Eric Botcazou @ 2003-10-11 6:38 UTC (permalink / raw)
To: Bradley Lucier; +Cc: gcc, libstdc++
> It seems that the g++ errors disappeared yesterday, but many of the
> libstdc++ ones remain:
>
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00446.html
The C++ errors have not totally disappeared: on 10/02, I had 7 unexpected C++
failures while there are still 42 unexpected failures according to your
report. I don't think we have recovered from the disastrous change yet.
--
Eric Botcazou
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-11 6:38 ` Eric Botcazou
@ 2003-10-11 6:44 ` Andreas Tobler
2003-10-11 10:11 ` Eric Botcazou
2003-10-13 17:08 ` Benjamin Kosnik
0 siblings, 2 replies; 18+ messages in thread
From: Andreas Tobler @ 2003-10-11 6:44 UTC (permalink / raw)
To: Eric Botcazou, Bradley Lucier; +Cc: gcc, libstdc++
Eric Botcazou wrote:
>>It seems that the g++ errors disappeared yesterday, but many of the
>>libstdc++ ones remain:
>>
>>http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00446.html
>
>
> The C++ errors have not totally disappeared: on 10/02, I had 7 unexpected C++
> failures while there are still 42 unexpected failures according to your
> report. I don't think we have recovered from the disastrous change yet.
>
With the patchlet we (mostly Pétur) found, the situation improves:
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00450.html
See also the follow up thread from this one.
http://gcc.gnu.org/ml/libstdc++/2003-10/msg00170.html
and back.
Still awaiting comments.
Andreas
RCS file: /cvs/gcc/gcc/libstdc++-v3/src/locale.cc,v
retrieving revision 1.95
diff -u -r1.95 locale.cc
--- src/locale.cc 2 Oct 2003 23:06:13 -0000 1.95
+++ src/locale.cc 9 Oct 2003 18:37:34 -0000
@@ -387,7 +387,6 @@
#ifdef __GTHREADS
if (__gthread_active_p())
__gthread_once(&_S_once, _S_initialize_once);
- else
#endif
{
if (!_S_classic)
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-11 6:44 ` Andreas Tobler
@ 2003-10-11 10:11 ` Eric Botcazou
2003-10-11 10:19 ` Andreas Tobler
2003-10-13 17:08 ` Benjamin Kosnik
1 sibling, 1 reply; 18+ messages in thread
From: Eric Botcazou @ 2003-10-11 10:11 UTC (permalink / raw)
To: Andreas Tobler; +Cc: Bradley Lucier, gcc, libstdc++
> With the patchlet we (mostly Pétur) found, the situation improves:
> http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00450.html
It's far better, indeed.
> See also the follow up thread from this one.
> http://gcc.gnu.org/ml/libstdc++/2003-10/msg00170.html
> and back.
Thanks for your effort in sorting this out!
--
Eric Botcazou
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-11 10:11 ` Eric Botcazou
@ 2003-10-11 10:19 ` Andreas Tobler
0 siblings, 0 replies; 18+ messages in thread
From: Andreas Tobler @ 2003-10-11 10:19 UTC (permalink / raw)
To: Eric Botcazou; +Cc: Bradley Lucier, gcc, libstdc++
Eric Botcazou wrote:
>>With the patchlet we (mostly Pétur) found, the situation improves:
>>http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg00450.html
>
>
> It's far better, indeed.
I have a multilib test running which shows better. I post as it finished.
>
>
>>See also the follow up thread from this one.
>>http://gcc.gnu.org/ml/libstdc++/2003-10/msg00170.html
>>and back.
>
>
> Thanks for your effort in sorting this out!
It was mostly learning for me, but quite useful.
Andreas
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-11 6:44 ` Andreas Tobler
2003-10-11 10:11 ` Eric Botcazou
@ 2003-10-13 17:08 ` Benjamin Kosnik
2003-10-13 17:34 ` Andreas Tobler
1 sibling, 1 reply; 18+ messages in thread
From: Benjamin Kosnik @ 2003-10-13 17:08 UTC (permalink / raw)
To: Andreas Tobler; +Cc: ebotcazou, lucier, gcc, libstdc++
So, what is the status of this patch? If it's to be something like this,
can you do a ChangeLog entry?
thanks,
benjamin
Index: src/locale.cc
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/src/locale.cc,v
retrieving revision 1.96
diff -c -p -r1.96 locale.cc
*** src/locale.cc 9 Oct 2003 21:17:11 -0000 1.96
--- src/locale.cc 13 Oct 2003 15:01:03 -0000
*************** namespace std
*** 395,406 ****
#ifdef __GTHREADS
if (__gthread_active_p())
__gthread_once(&_S_once, _S_initialize_once);
- else
#endif
! {
! if (!_S_classic)
! _S_initialize_once();
! }
}
void
--- 395,403 ----
#ifdef __GTHREADS
if (__gthread_active_p())
__gthread_once(&_S_once, _S_initialize_once);
#endif
! if (!_S_classic)
! _S_initialize_once();
}
void
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Heads up: Several thousand g++ and libstdc++ test failures on sparc[64]
2003-10-13 17:08 ` Benjamin Kosnik
@ 2003-10-13 17:34 ` Andreas Tobler
0 siblings, 0 replies; 18+ messages in thread
From: Andreas Tobler @ 2003-10-13 17:34 UTC (permalink / raw)
To: Benjamin Kosnik; +Cc: Pétur Runólfsson, gcc, libstdc++
Benjamin Kosnik wrote:
>
>
> So, what is the status of this patch? If it's to be something like this,
> can you do a ChangeLog entry?
Ah!?
Certainly can I write a ChangeLog entry, if this IS the solution.
But what do I write?
Workaround for a solaris bug?
Andreas
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2003-10-13 16:35 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-03 14:23 Heads up: Several thousand g++ and libstdc++ test failures on sparc[64] Bradley Lucier
2003-10-03 14:51 ` Eric Botcazou
2003-10-03 15:41 ` Benjamin Kosnik
2003-10-03 16:00 ` Andreas Tobler
2003-10-03 17:59 ` Gabriel Dos Reis
2003-10-03 18:03 ` Andreas Tobler
2003-10-03 21:32 ` Zack Weinberg
2003-10-03 21:47 ` Gabriel Dos Reis
2003-10-04 3:56 ` Bradley Lucier
2003-10-09 16:04 ` Eric Botcazou
2003-10-03 15:42 ` Bradley Lucier
2003-10-10 20:35 ` Bradley Lucier
2003-10-11 6:38 ` Eric Botcazou
2003-10-11 6:44 ` Andreas Tobler
2003-10-11 10:11 ` Eric Botcazou
2003-10-11 10:19 ` Andreas Tobler
2003-10-13 17:08 ` Benjamin Kosnik
2003-10-13 17:34 ` Andreas Tobler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).