From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: ACATS & dispatching priorities
Date: Tue, 9 May 2017 14:41:47 -0500
Organization: JSA Research & Innovation
Message-ID: <oet61r$55f$1@franka.jacob-sparre.dk>
References: 
 <lybmr7jjxa.fsf@pushface.org><be8700bd-c6e9-43fb-b37d-72a237619818@googlegroups.com>
 <ly7f1sjtl7.fsf@pushface.org>
NNTP-Posting-Host: rrsoftware.com
X-Trace: franka.jacob-sparre.dk 1494358908 5295 24.196.82.226 (9 May 2017
 19:41:48 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Tue, 9 May 2017 19:41:48 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Xref: news.eternal-september.org comp.lang.ada:46732
Date: 2017-05-09T14:41:47-05:00
List-Id: <comp.lang.ada>

Given that 98% of the ACATS tests are older than System.Multiprocessors, 
it's not surprising that they don't use it. On top of which, no tests using 
that package would work on compilers older than Ada 2012 (we still maintain 
Ada 95 and Ada 2005 versions of the test suite, in part so it is isn't a 
GNAT-only endevour).

                        Randy.

"Simon Wright" <simon@pushface.org> wrote in message 
news:ly7f1sjtl7.fsf@pushface.org...
> Robert Eachus <rieachus@comcast.net> writes:
>
>> On Friday, May 5, 2017 at 1:24:51 PM UTC-4, Simon Wright wrote:
>>> ACATS 4.1 has tests CXD* which test correct Annex D behaviour. I'm
>>> getting problems with them. See [0] for work in progress.
>>
>> The ACATS tests should have notations as to which tests are not
>> appropriate for a system with multiple processor cores.  Do you by
>> chance have that problem?
>
> A good thought; I was expecting the number of cores to be automatically
> detected, but no (I think maybe it should be now we have
> System.Multiprocessors).
>
> I still have issues, but I think they are all locking-related now.