Re: Volunteer for bug summaries?

[Brooks Moses <brooks dot moses at codesourcery dot com>]

Mark Mitchell wrote:
> 1. Add a field to bugzilla for the SVN revision at which a particular
> regression was introduced.  Display that in bugzilla as a link to the
> online SVN history browser so that clicking on a link takes us from the
> PR straight to the checkin.  This field value ought to be the most
> recent revision to the GCC trunk such that the bug did not occur in the
> previous revision, but does occur in all subsequent revisions.

In practice, it seems that in conversations here this is often reported 
as a range -- it is known to work at SVN revision N, but fails at 
revision N+5 or somesuch.  Might it be useful to have some way of 
recording this, rather than expecting a single number?

This also has the advantage that it can be incrementally improved, 
rather than needing to be filled in all at once.  (For instance, a value 
of "known to fail" can be filled in when the bug is confirmed, and may 
be useful if the bug lasts for a while.)

Also, there's the point that the compiler is occasionally broken on some 
targets.  If a regression occurs during one of these "dark ages", it 
can't be tracked down to a single commit solely by testing.

- Brooks