This is the mail archive of the
mailing list for the GCC project.
Re: Bug maintenance
- From: Oleg Endo <oleg dot endo at t-online dot de>
- To: David Wohlferd <dw at LimeGreenSocks dot com>, Martin Sebor <msebor at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 09 May 2016 07:13:05 +0900
- Subject: Re: Bug maintenance
- Authentication-results: sourceware.org; auth=none
- References: <f6229fa4-9877-f6fc-fc4e-bd011e1720cd at LimeGreenSocks dot com> <57223D52 dot 20409 at gmail dot com> <5b3e7846-fa79-7d90-0871-2d2b35027f11 at LimeGreenSocks dot com>
On Sun, 2016-05-08 at 15:03 -0700, David Wohlferd wrote:
> On 4/28/2016 9:41 AM, Martin Sebor wrote:
> > On 04/28/2016 01:35 AM, David Wohlferd wrote:
> > > As part of the work I've done on inline asm, I've been looking
> > > thru the
> > > bugs for it. There appear to be a number that have been fixed or
> > > overtaken by events over the years, but the bug is still open.
> > >
> > > Is closing some of these old bugs of any value?
> > >
> > > If so, how do I pursue this?
> > There are nearly 10,000 still unresolved bugs in Bugzilla, almost
> > half of which are New, and a third Unconfirmed, so I'm sure any
> > effort to help reduce the number is of value and appreciated.
> That's exactly what prompted me to ask. There's such a vast number
> of them, it's hard to believe that 9 year old bugs are still of
Sometimes there is. Before randomly closing any bugs because they are
too old, one should at least have a look at them and see if they're
still an issue etc. Often things would've been fixed along the way,
but not all of them.