From: Benjamin Kosnik <bkoz@redhat.com>
To: libstdc++@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: mainline libstdc++ failures, one week old
Date: Wed, 08 Sep 2004 16:48:00 -0000 [thread overview]
Message-ID: <20040908114741.25e2d1b7.bkoz@redhat.com> (raw)
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
next reply other threads:[~2004-09-08 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 16:48 Benjamin Kosnik [this message]
2004-09-08 16:57 ` Andrew Pinski
2004-09-11 0:18 ` Mike Stump
2004-09-17 18:15 ` Benjamin Kosnik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040908114741.25e2d1b7.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).