Re: GCC 4.2.0 Status Report (2007-04-15)

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Janis" == Janis Johnson <janis187@us.ibm.com> writes:

>> * Very few people know how to use Janis' scripts, so to encourage
>> people to use them, the release manager could write a wiki page with a
>> HOWTO for these scripts (or ask someone to do it).  Regression hunting
>> should only be easier now, with SVN's atomic commits. But the easier
>> and more accessible you make it for people to use the available tools,
>> the harder it gets for people to justify ignoring their bugs to "the
>> rest of us".

Janis> The RM can encourage me to do this; I've already been meaning to for a
Janis> long time now.

Janis> My reghunt scripts have grown into a system that works well for me, but
Janis> I'd like to clean them up and document them so that others can use them.
Janis> What I've got now is very different from what I used with CVS.

I wonder whether there is a role for the gcc compile farm in this?
For instance perhaps "someone" could keep a set of builds there and
provide folks with a simple way to regression-test ... like a shell
script that takes a .i file, ssh's to the farm, and does a reghunt... ?

I think this would only be worthwhile if the farm has enough disk, and
if regression hunting is a fairly common activity.

Tom