From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_05,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.5-pre1
X-Received: by 2002:a37:59c7:: with SMTP id n190mr10164677qkb.146.1623531003241;
        Sat, 12 Jun 2021 13:50:03 -0700 (PDT)
X-Received: by 2002:a25:4009:: with SMTP id n9mr14126102yba.73.1623531003055;
 Sat, 12 Jun 2021 13:50:03 -0700 (PDT)
Path: eternal-september.org!reader02.eternal-september.org!news.mixmin.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 12 Jun 2021 13:50:02 -0700 (PDT)
In-Reply-To: <iikb6gFrhljU1@mid.individual.net>
Injection-Info: google-groups.googlegroups.com; posting-host=174.71.119.33; posting-account=ix5KpAoAAAD9zo_4u1FxHVmn1uZn7U_d
NNTP-Posting-Host: 174.71.119.33
References: <c6169572-25bc-4db7-a50d-c6c8575069a4n@googlegroups.com>
 <sa2bpc$it8$1@gioia.aioe.org> <aa8d1e4f-494e-4d8a-8c44-edfdb7f3ec04n@googlegroups.com>
 <4db69f85-a3b3-48f8-a41e-8bdf196a8294n@googlegroups.com> <iikb6gFrhljU1@mid.individual.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <78d187a6-2739-4ae0-b91e-acaa8438ecden@googlegroups.com>
Subject: Re: non-preemptive tasking on GNAT 2020 Windows 10 multicore AMD
From: Dan Winslow <dandwinslow@gmail.com>
Injection-Date: Sat, 12 Jun 2021 20:50:03 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:62205
List-Id: <comp.lang.ada>

On Saturday, June 12, 2021 at 1:02:58 PM UTC-5, Niklas Holsti wrote:
> On 2021-06-12 19:03, AdaMagica wrote:=20
> > There is another importatn point. X and Y are global, and a task may=20
> > update globals only at dispatching points.
> Updates to globals can be delayed, yes. But where in the RM does it say=
=20
> that a task cannot delay updates to non-volatile globals past=20
> dispatching points?=20
>=20
> I haven't found any connection between dispatching points and updates to=
=20
> globals in RM Annex D, where dispatching points are defined.
> > So taks One could infact consider Y constant within the loop.
> Yes.

Yes, that was my thought too, but I'm no expert. These tasks have no dispat=
ches at all, that's the point. I expected whichever one started first to ru=
n to completion, then the other while main was pending exit (or looping, as=
 I set up later). They were both on the same CPU, non-preemptive was set, y=
et they clearly task switched.