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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ce667ecdc314f22 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-03-08 06:40:05 PST Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!newsfeed.berkeley.edu!ucberkeley!cyclone.swbell.net!nnrp2.sbc.net.POSTED!not-for-mail From: "Pat Rogers" Newsgroups: comp.lang.ada References: <3AA692A8.F1283C27@netscape.net> <87bsrcs8a3.fsf@deneb.enyo.de> Subject: Re: Releasing Aliased Variables X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: Date: Thu, 8 Mar 2001 08:37:29 -0600 NNTP-Posting-Host: 208.191.184.67 X-Complaints-To: abuse@swbell.net X-Trace: nnrp2.sbc.net 984062251 208.191.184.67 (Thu, 08 Mar 2001 08:37:31 CST) NNTP-Posting-Date: Thu, 08 Mar 2001 08:37:31 CST Organization: SBC Internet Services Xref: supernews.google.com comp.lang.ada:5543 Date: 2001-03-08T08:37:29-06:00 List-Id: "Florian Weimer" wrote in message news:87bsrcs8a3.fsf@deneb.enyo.de... > Robert A Duff writes: > > > In code-generation terms, it causes X to allocated at an addressable > > location (eg, not in a register). It is unlikely that "aliased" > > controls whether X is allocated on the stack versus the heap (but of > > course compilers can do what they like). > > Some time ago, there was a thread in which someone explained (I think > Robert Dewar) that 'aliased' does not provide any help to the compiler > regarding alias detection, register allocation etc. because the > compiler has to be able to determine this kind of information anyway > if an Address attribute is used. Did you mean "Access" instead of "Address"? > So in code-generation terms, 'aliased' is a no-op. Unless that part of the code generation is deferred to link time (which happens for other things), I don't see how that can cover the case of separately compiled code -- one containing the declaration and the other containing the corresponding 'Access.