Using bugzilla to track XFAILs

[Richard Earnshaw]

> "Giovanni Bajo" <giovannibajo@libero.it> writes:
> 
> > There must be a better way to not forget about them. I propose the introduce a
> > new policy: for each regression which has been xfailed in the testsuite, there
> > ought be a bugzilla bug referencing it. We already have a keyword called
> > 'xfail', but it is currently used only by the tree-ssa branch.
> 
> I second this proposal.
> 
> Ian

I like the idea also, but we need to make sure we do it carefully.  Often 
a test is xfailed when it isn't really a problem with the compiler but 
with the run-time environment.  Take, for example, 
g77.f-torture/execute/io0.f, which is xfailed on several embedded 
platforms because there is no support for stat() in these environments.

Ideally such tests should be skipped when the compiler is not at fault.

Another possibility might be to use the KFAIL feature introduced into 
dejagnu for gdb.  A kfail (known failure) could require a PR to be 
associated with it.

R.