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!mx02.eternal-september.org!.POSTED!not-for-mail
From: Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Newsgroups: comp.lang.ada
Subject: Re: STM32F4 GNAT Run Time System - roadmap
Date: Wed, 9 Dec 2015 18:46:42 -0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <n49suh$en8$1@dont-email.me>
References: <lyzj49qecx.fsf@pushface.org> <ml96i2$3qs$2@dont-email.me>
 <lya8pnh1dq.fsf@pushface.org> <n45e84$rpr$1@loke.gir.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 9 Dec 2015 18:46:42 -0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="efef809c78890c63375ef4dfd3331232";
	logging-data="15080"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/Roi0yiKoP2OuXo9DzkVW3EBMFI4U+yIs="
User-Agent: slrn/0.9.9p1 (Linux)
Cancel-Lock: sha1:VMWDu6WKWAVx42ycgYjLvmJFFjI=
Xref: news.eternal-september.org comp.lang.ada:28742
Date: 2015-12-09T18:46:42+00:00
List-Id: <comp.lang.ada>

On 2015-12-08, Randy Brukardt <randy@rrsoftware.com> wrote:
> "Simon Wright" <simon@pushface.org> wrote in message 
> news:lya8pnh1dq.fsf@pushface.org...
>> ...I've not done any evaluation yet
>> aside from noting that they generate the GNAT-specific
>> Volatile_Full_Access aspect, which is noted in the 'under development'
>> version of the GCC docs (so, will likely be in GCC 6). Maybe plain
>> Volatile will do (but users would have to remember to access the whole
>> register explicitly, rather than leaving it up to the compiler to Do The
>> Right Thing); that would be an easy-enough patch.
>
> The ARG has decided on a different direction to fix the problem addressed by 
> Volatile_Full_Access; essentially, accesses to non-volatile components of 
> atomic objects have to be accessed with a read-modify-write cycle. (See 
> AI12-0128-1.) Various parts of Annex C will be rewritten to make that make 
> sense.
>

Hmm, one of the two I submitted last year. :-) Nice to see it moving forward.

What's the general feeling within the ARG about the related AI12-0127-1
partial aggregate notation proposal, especially as it applies to updating
bitfields within device registers ? How likely is that to happen ?

Thanks,

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world