From: Joe Buck <Joe.Buck@synopsys.COM>
To: Paul Brook <paul@codesourcery.com>
Cc: gcc@gcc.gnu.org, Steven Bosscher <stevenb.gcc@gmail.com>, hp@gcc.gnu.org
Subject: Re: Regression count, and how to keep bugs around forever
Date: Wed, 19 Dec 2007 01:46:00 -0000 [thread overview]
Message-ID: <20071219013529.GN2908@synopsys.com> (raw)
In-Reply-To: <200712190125.21231.paul@codesourcery.com>
On Wed, Dec 19, 2007 at 01:25:19AM +0000, Paul Brook wrote:
> On Wednesday 19 December 2007, Joe Buck wrote:
> > On Wed, Dec 19, 2007 at 01:11:11AM +0000, Paul Brook wrote:
> > > > So I'm asking for a policy here that says when it is OK to resolve old
> > > > bug without progress as WONTFIX or SUSPENDED. Start shooting.
> > >
> > > I think this would be a big mistake to reuse an existing state for this.
> >
> > But this is pretty much what SUSPENDED means; it means that there's no
> > intent to work on the bug in the near term.
>
> Ok. I did check the GCC bugzilla help pages, and they don't mention SUSPENDED
> at all :-)
Patches welcome, as they say.
We have 91 bugs in the SUSPENDED state. Many of them are odd corners of
the standard where we're waiting for the appropriate committee to decide
what the correct behavior is; others are ancient bugs that we've just
agreed to live with. The oldest one relates to the issue of extra FPU
precision on x86.
next prev parent reply other threads:[~2007-12-19 1:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 1:11 Steven Bosscher
2007-12-19 1:14 ` Paul Brook
2007-12-19 1:21 ` Joe Buck
2007-12-19 1:35 ` Paul Brook
2007-12-19 1:46 ` Joe Buck [this message]
2007-12-19 3:16 ` Joe Buck
2007-12-19 5:16 ` David Daney
2007-12-19 1:58 ` Joseph S. Myers
2007-12-26 19:25 ` Mark Mitchell
2007-12-19 5:15 ` Weddington, Eric
2007-12-19 14:22 ` Manuel López-Ibáñez
2007-12-19 15:59 ` Rask Ingemann Lambertsen
2007-12-19 22:19 ` Steven Bosscher
2007-12-20 0:10 ` Rask Ingemann Lambertsen
2007-12-20 1:25 ` NightStrike
2007-12-20 5:05 ` David Daney
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=20071219013529.GN2908@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=hp@gcc.gnu.org \
--cc=paul@codesourcery.com \
--cc=stevenb.gcc@gmail.com \
/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).