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: 
 border2.nntp.dca1.giganews.com!nntp.giganews.com!news.alt.net!news.ecp.fr!news.stack.nl!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Newsgroups: comp.lang.ada
Subject: Re: Modified proposals for Ada-Comment
Date: Thu, 17 Jul 2014 21:15:14 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <lq9ed2$cbt$1@dont-email.me>
References: <lprvo8$mcl$1@dont-email.me> <c2dotiF8chiU1@mid.individual.net>
Injection-Date: Thu, 17 Jul 2014 21:15:14 +0000 (UTC)
Injection-Info: mx05.eternal-september.org;
 posting-host="e458ff8b81bc0c159989eb0e36c6e372";
 logging-data="12669"; mail-complaints-to="abuse@eternal-september.org";
 posting-account="U2FsdGVkX1/97JQDdDhJYkyA9KyA+KRUOvAxkJFpENo="
User-Agent: slrn/0.9.8.1 (VMS/Multinet)
Cancel-Lock: sha1:WKgvN9bn0R7iaXcyH1RdDzgwOWk=
Xref: number.nntp.dca.giganews.com comp.lang.ada:187678
Date: 2014-07-17T21:15:14+00:00
List-Id: <comp.lang.ada>

On 2014-07-12, Niklas Holsti <niklas.holsti@tidorum.invalid> wrote:
>
> Might you include in this question also whether increasing the size of
> an atomic object using a 'Size clause means that the atomic access
> should apply to all the bits included in 'Size, and not just to the bits
> included in the declared components of the object?
>

The response (from Tucker Taft) I got to your 'Size question was this:

My original question as submitted:

||    As a related question, when C.6(15) does apply, does it also apply to
||    all the bits included by 'Size when 'Size has been used to increase
||    the size of the atomic object (say from 5 bits to 32 bits) ?
||

The response:

|
|The definition of 'Size on an elementary object is that it refers to the
|number of bits normally read/written, as specified in 13.1(7/2):
|
|  "The representation of an object consists of a certain number of bits
|  (the size of the object). For an object of an elementary type, these are
|  the bits that are normally read or updated by the machine code when
|  loading, storing, or operating-on the value of the object...."
|
|For a non-atomic composite object, extra bits might not be loaded/stored,
|again quoting from that same paragraph:
|
|  "... For a composite object, padding bits might not be read or updated in
|  any given composite operation, depending on the implementation."
|
|For an atomic composite object, although it is not stated explicitly, the
|implication is that the 'Size of an atomic object determines the number of
|bits read/written indivisibly (e.g. see C.6(11/4)).

On a related matter, the responses to the C.6(15) question about if
Atomic on a record applies to it's components, are in the general
direction of no it doesn't.

Simon.

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