public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* mainline libstdc++ failures, one week old
@ 2004-09-08 16:48 Benjamin Kosnik
  2004-09-08 16:57 ` Andrew Pinski
  2004-09-11  0:18 ` Mike Stump
  0 siblings, 2 replies; 4+ messages in thread
From: Benjamin Kosnik @ 2004-09-08 16:48 UTC (permalink / raw)
  To: libstdc++; +Cc: gcc

This is just a heads up to libstdc++ developers.

Last known good snapshot of mainline with zero libstdc++ failures on
x86/linux or ppc/darwin is Sept 1 or 2, depending on your location and
pull date.

See:

http://gcc.gnu.org/ml/gcc-testresults/2004-09/msg00059.html
vs.
http://gcc.gnu.org/ml/gcc-testresults/2004-09/msg00292.html

So, things have been broken for some time.

Is there any effort at fixing this breakage? I do not see this as
library-related, but compiler related. Thoughts?

-benjamin

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: mainline libstdc++ failures, one week old
  2004-09-08 16:48 mainline libstdc++ failures, one week old Benjamin Kosnik
@ 2004-09-08 16:57 ` Andrew Pinski
  2004-09-11  0:18 ` Mike Stump
  1 sibling, 0 replies; 4+ messages in thread
From: Andrew Pinski @ 2004-09-08 16:57 UTC (permalink / raw)
  To: Benjamin Kosnik; +Cc: libstdc++, gcc


On Sep 8, 2004, at 9:47 AM, Benjamin Kosnik wrote:

> This is just a heads up to libstdc++ developers.
>
> Last known good snapshot of mainline with zero libstdc++ failures on
> x86/linux or ppc/darwin is Sept 1 or 2, depending on your location and
> pull date.
>
> See:
>
> http://gcc.gnu.org/ml/gcc-testresults/2004-09/msg00059.html
> vs.
> http://gcc.gnu.org/ml/gcc-testresults/2004-09/msg00292.html
>
> So, things have been broken for some time.
>
> Is there any effort at fixing this breakage? I do not see this as
> library-related, but compiler related. Thoughts?

Yes see:
<http://gcc.gnu.org/ml/gcc-regression/2004-09/msg00008.html>
Which shows the 8 related C++ regressions which are the same
breakage as the libstdc++ ones.

Thanks,
Andrew Pinski

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: mainline libstdc++ failures, one week old
  2004-09-08 16:48 mainline libstdc++ failures, one week old Benjamin Kosnik
  2004-09-08 16:57 ` Andrew Pinski
@ 2004-09-11  0:18 ` Mike Stump
  2004-09-17 18:15   ` Benjamin Kosnik
  1 sibling, 1 reply; 4+ messages in thread
From: Mike Stump @ 2004-09-11  0:18 UTC (permalink / raw)
  To: Benjamin Kosnik; +Cc: libstdc++, gcc

On Wednesday, September 8, 2004, at 09:47  AM, Benjamin Kosnik wrote:
> This is just a heads up to libstdc++ developers.
>
> Last known good snapshot of mainline with zero libstdc++ failures on
> x86/linux or ppc/darwin is Sept 1 or 2, depending on your location and
> pull date.

I think this has just been fixed:

http://gcc.gnu.org/ml/gcc-patches/2004-09/msg01018.html

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: mainline libstdc++ failures, one week old
  2004-09-11  0:18 ` Mike Stump
@ 2004-09-17 18:15   ` Benjamin Kosnik
  0 siblings, 0 replies; 4+ messages in thread
From: Benjamin Kosnik @ 2004-09-17 18:15 UTC (permalink / raw)
  To: Mike Stump; +Cc: libstdc++, gcc


This is now fixed completely. 

Thanks Diego!

-benjamin

>> Last known good snapshot of mainline with zero libstdc++ failures on
>> x86/linux or ppc/darwin is Sept 1 or 2, depending on your location and
>> pull date.

^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-09-17 16:44 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-08 16:48 mainline libstdc++ failures, one week old Benjamin Kosnik
2004-09-08 16:57 ` Andrew Pinski
2004-09-11  0:18 ` Mike Stump
2004-09-17 18:15   ` Benjamin Kosnik

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).