public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gypsy@Media.mit.edu, nobody@gcc.gnu.org Subject: Re: bootstrap/7509: gcc 3.1.1 bootstrap fails in stage2 Date: Thu, 05 Dec 2002 13:32:00 -0000 [thread overview] Message-ID: <20021205213237.11047.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1555 bytes --] Synopsis: gcc 3.1.1 bootstrap fails in stage2 State-Changed-From-To: open->closed State-Changed-By: bangerth State-Changed-When: Thu Dec 5 13:32:37 2002 State-Changed-Why: Based on the following mail, I close all except 6680. Date: Thu, 5 Dec 2002 10:54:36 +0100 From: Emmanuel Thomé <thome@lix.polytechnique.fr> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Subject: Re: ICE/bootstrap alpha*-dec-osf5.0 OK, I'll contact the persons you mention. > > P.S: Perhaps most if not all of these PR's could be collapsed to a > > single one ? > > [...] > > Oh yes, I would be happy to do this. Can you indicate which of these I can > close and which other report I should reference in the closing message? > The bug database has become so large that it has become nearly unusable, > and it is really necessary to reduce same cases to only one > representative. Then I'm 100% sure that PRs # 6680, 6766, 7509, 7626, 7747, 7777, 8452, 6796 are duplicates of the same bug. The six other PRs I mention in my mail might be related to the same issue, but that's unclear. So this makes for 8 PRs that you can collapse into a single one ! None of them is significantly more accurate than the others, so picking a random one would do. Perhaps the one PR that you keep should include a reference to the ones that have been closed. Greetings, E. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7509
next reply other threads:[~2002-12-05 21:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-05 13:32 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-06 10:46 gypsy
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=20021205213237.11047.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gypsy@Media.mit.edu \ --cc=nobody@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: linkBe 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).