This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Policy for wrong-code bugs
- From: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: ebotcazou at libertysurf dot fr
- Cc: mark at codesourcery dot com, Joe dot Buck at synopsys dot COM, gcc at gcc dot gnu dot org
- Date: Tue, 13 Jul 2004 09:46:32 +0200 (CEST)
- Subject: Re: Policy for wrong-code bugs
On 13 Jul, Eric Botcazou wrote:
>> I think that Volker's proposal makes sense in the abstract, but will be
>> confusing in practice. People are still using really old compilers --
>> we have a customer where we are still supporting GCC 2.8.1, for
>> example. Keeping PRs open for all current, shipping compilers means
>> never closing any PR ever.
>
> I don't think that's what Volker meant. He said: "I think we should close
> them, only if they are fixed on mainline *and* all open release branches (or
> if explicitly marked as WON'T FIX on those branches)." For the FSF
> compilers, this currently means the 3.3 and 3.4 branches.
Yup. That's what I meant.
> I think this would make sense, in that this would force an explicit decision
> from the respective RMs for their branch, instead of the current situation
> where bugs are silently closed and not fixed on the branches.
Right. And given how much pain it can be to identify wrong-code bugs
(I remember several nasty POOMA testcases) the decision to say "WON'T
FIX" or not should be taken seriously.
Regards,
Volker