This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: bugs fixed on the tree-ssa

From: Daniel Berlin <dberlin at dberlin dot org>
To: mark at codesourcery dot com
Cc: Joe Buck <Joe dot Buck at synopsys dot COM>,Giovanni Bajo <giovannibajo at libero dot it>,gcc at gcc dot gnu dot org,Richard Guenther <rguenth at tat dot physik dot uni-tuebingen dot de>,Bugzilla Masters <bugzilla-masters at dberlin dot org>,Andrew Pinski <pinskia at physics dot uc dot edu>
Date: Sun, 28 Dec 2003 13:46:00 -0500
Subject: Re: bugs fixed on the tree-ssa
References: <Pine.LNX.4.53.0312171041240.6232@bellatrix.tat.physik.uni-tuebingen.de> <0a4701c3c492$6206ada0$55bb2997@bagio> <1072635697.10278.49.camel@doubledemon.codesourcery.com>

On Dec 28, 2003, at 1:21 PM, Mark Mitchell wrote:

I agree. Suspended looks like an appropriate state for me. Let's just wait until the merge really happens, and then we can revisit the bugs. Meanwhile, it might be useful to add the testcases for the bugs to the branch, so that we can reasonably sure that they stay fixed.
The right solution is clear: there should be a per-branch state for
bugs, or, equivalently, bug-state keywords on a per-branch basis.

Actually, what we've been working on is somewhat similar a "known to work" field that lists versions the bug is known to be fixed in a "known to fail" field that lists versions the bug is known not to be fixed in

Follow-Ups:
- Re: bugs fixed on the tree-ssa
  - From: Mark Mitchell

References:
- Re: bugs fixed on the tree-ssa
  - From: Richard Guenther
- Re: bugs fixed on the tree-ssa
  - From: Giovanni Bajo
- Re: bugs fixed on the tree-ssa
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]