Re: Technique for finding regressions in the C++ parser

[Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>]

Hi,

how about a script that does the patch-hunting proposed by Craig?
Something that can be invoked like

PatchHunter command result before|after startdate enddate

where
* "command" is the command that will be executed after each
  compiler-build (most likely something like "g++ -c bug.cc"
  - but you could also do "g++ bug.cc; ./a.out")
* "result" is a number or "ICE" (in the first case the result
  of the command will be compared to this number, in the second case
  it will be cheked whether an ICE occured or not.
* "before|after" means that "result" is the expected behaviour
  "before|after" the patch we're searching for (this is a little
  bit redundant, since the script could find that out itself).
* startdate and enddate are obvious

This way one could find patches that cause bugs and patches that fix
them. I'd very much appreciate starting my computer in the evening
and come back in the morning with the patch I was looking for on
the screen.

Any volunteers or other suggestions?

Regards,
Volker