email-based regression search server

Phil Edwards phil@jaj.com
Wed Feb 5 23:34:00 GMT 2003


On Wed, Feb 05, 2003 at 03:05:54PM -0800, Joe Buck wrote:
> On Wed, Feb 05, 2003 at 02:43:49PM -0500, Phil Edwards wrote:
> > It can now also look for the opposite situation:  the input code was broken,
> > but now compiles.  (I don't know of an example.)
> 
> One reason someone might want that is if they know that someone fixed
> a failure on one branch, and they want to figure out what the fix was,
> for the purpose of porting the fix to another branch.

Well said.


> If instead you have
> 
> P P F F P P P P F F F F
> 
> then you know that you will find an F that is immediately preceded by
> a P, but you don't know which one you'll get.

The way the script works, you will almost certainly get "the wrong one,"
and I'd hate to hold hope of anything different.

Maybe I should offer a linear search mode as an option, with output like

    yyyy-mm-dd  P
    yyyy-mm-dd  F
    yyyy-mm-dd  P
    yyyy-mm-dd  P
    yyyy-mm-dd  F
    yyyy-mm-dd  P
    ...


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002



More information about the Gcc mailing list