C identifier lookup speedups, 1/2

Richard Earnshaw rearnsha@arm.com
Wed Apr 16 15:25:00 GMT 2003

> David Edelsohn <dje@watson.ibm.com> writes:
> >>>>>> Zack Weinberg writes:
> >
> > Zack> Yes.  It is supposed to be XFAILed.  Please find out why
> > Zack> builtin-noret-2.x isn't doing its job.
> >
> > 	It is XFAILED, but XFAIL applies to a FAIL.  Because of the link
> > error, the case is UNRESOLVED.  XFAIL try to build and execute it, but
> > expect FAIL.
> But the link error *is* the expected failure mode, so the XFAIL
> marker is applied to the compile phase.  This works for me; why is
> dejagnu giving you an UNRESOLVED?

The compile test is XFAILing (at least, that's the behaviour on ARM); but 
because the test failed to compile, the execution test can't run.  Hence 
the UNRESOLVED -- we don't know if the test runs correctly, because we 
can't build it.  Of course, after an XFAIL during compile, it could be 
argued that the result of the execution test should be XUNRESOLVED...


More information about the Gcc-patches mailing list