RFC: Change rules for adding/changing test cases

[Richard Earnshaw]

> 
> > I definitely agree with the last point. What we do in the GNAT project is
> > to assign a tracking number to every problem report. The test case is filed
> > under this tracking number, and all revision history entries (which are 
> > always detailed, and include how and why the problem was fixed) also include
> > this same tracking number.
> 
> As I mentioned in another mail, not all gcc testcases have
> corresponding bug reports to refer to, and it's not always efficient
> to rely on a database halfway across the Internet to give you clues
> about how to fix bugs a testcase catches.

But equally, the reason why a test fails on one target may be completely 
different from the reason why it fails on another; so I see minimal uses 
for such comments.  In the end, the only real way to debug a problem is to 
run the compiler under a debugger and look at what is really going wrong.

R.