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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,be920da40970e1c2
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2000-11-01 20:55:41 PST
Path: 
 supernews.google.com!sn-xit-02!sn-xit-03!supernews.com!europa.netcrusader.net!205.252.116.205!howland.erols.net!newshub2.home.com!news.home.com!news1.sttls1.wa.home.com.POSTED!not-for-mail
Reply-To: "DuckE" <nospam_steved94@home.com>
From: "DuckE" <nospam_steved94@home.com>
Newsgroups: comp.lang.ada
References: <3A007357.FF3475A0@mindspring.com> <8tpvpl$ige$1@nnrp1.deja.com>
Subject: Re: gnat/ppc and a32 blt transfers
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Message-ID: <ct6M5.42679$E85.1088500@news1.sttls1.wa.home.com>
Date: Thu, 02 Nov 2000 04:55:36 GMT
NNTP-Posting-Host: 24.6.221.63
X-Complaints-To: abuse@home.net
X-Trace: news1.sttls1.wa.home.com 973140936 24.6.221.63 (Wed,
 01 Nov 2000 20:55:36 PST)
NNTP-Posting-Date: Wed, 01 Nov 2000 20:55:36 PST
Organization: @Home Network
Xref: supernews.google.com comp.lang.ada:1704
Date: 2000-11-02T04:55:36+00:00
List-Id: <comp.lang.ada>

Should't

 pragma Atomic( variable );

cause accesses to a variable to be performed as a single operation?

While I would not expect this to work for the component of a packed boolean
array, since  element is not individually addessable (on most
architectures), I would expect this functionality using types that are
individually addressable.

For example, on an architecture where integers are 32 bit values I would
expect the following declarations:

  memValue : Integer;
  FOR memValue'ADDRESS USE
System.Storage_Elements.To_Address( 16#FFFE0000# );
  PRAGMA Atomic( memValue );

To generate code that uses 32 bit accesses to memValue.

Since GNAT supports Annex C, and this behaviour is described in C.6.15, I
would expect this behavior.

Am I missing something?

SteveD