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-Thread: 103376,ffda156586947522 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!news.glorb.com!feeder.erje.net!news.osn.de!diablo1.news.osn.de!noris.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: volatile vs volatile_components Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <046f172d-90f7-4a23-a181-dd1461ebd94b@i18g2000prf.googlegroups.com> <249486d2-c000-483f-af5b-4938ba6ccc51@b2g2000prf.googlegroups.com> Date: Thu, 6 Nov 2008 10:25:15 +0100 Message-ID: NNTP-Posting-Date: 06 Nov 2008 10:25:15 CET NNTP-Posting-Host: edcd0837.newsspool3.arcor-online.net X-Trace: DXC=TFX@\CZm6Gi016@cHD@m;jMcF=Q^Z^V3h4Fo<]lROoRa^YC2XCjHcbiN8@>nj\>j@iDNcfSJ;bb[eFCTGGVUmh?dLK[5LiR>kgb>FV7YK8]L5e X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:2594 Date: 2008-11-06T10:25:15+01:00 List-Id: On Wed, 5 Nov 2008 17:21:25 -0800 (PST), Adam Beneschan wrote: > I can't think of a single case where an operation on an array > that has Volatile_Components but not Volatile specified should behave > differently than the same operation on a Volatile array. Packed; cached arrays? I would guess that when the array is volatile, but its components are not, then subsequent reading two components occupying the same memory location can be coalesced into one memory operation. It would store things into; say; a register and the components would be obtained from there. When the components are volatile the compiler must read the memory twice. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de