Re: Formal Subprogram Access

[Simon Wright <simon@pushface.org>]

Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> writes:

> On 2018-02-14, Randy Brukardt <randy@rrsoftware.com> wrote:
>>
>> "Simon Wright" <simon@pushface.org> wrote in message 
>> news:lymv0bk59g.fsf@pushface.org...
>>>
>>> Good news!
>>>
>>> For info, my current 8.0.1 20180207 results, vs 4.1f, are
>>>
>>> # of expected passes 2500
>>> # of unexpected failures 9
>>> # of expected failures 1451
>>> # of unresolved testcases 11
>>> # of unsupported tests 121
>>> *** FAILURES: c250002  cxd1003 cxd1004 cxd1005 cxd4007  cxd2006 cxd3001 
>>> cxd3002  c611a04
>>
>> This is similar to the list of C-Tests that the ACATS tools report as 
>> failed.
>>
>
> Does the testsuite also report the number of unexpected passes ?

It would if there were any.

> I don't see a line for that above, and if the number is zero, I would
> expect to see a line of output confirming that.

So far as I can tell, this behaviour is consistent with other GCC
tests. Certainly with "make check-gnat".

The GCC ACATS tests are run by a shell script, unlike all (?) the other
tests which are run via dejagnu, and the current script in GCC 
reports PASSes and FAILs unconditionally and UNSUPPORTED if non-zero (it
doesn't check XPASS, because it doesn't run B or L tests which are the
ones expected to fail).