Re: Releasing Aliased Variables

["Pat Rogers" <progers@NOclasswideSPAM.com>]

"Florian Weimer" <fw@deneb.enyo.de> wrote in message
news:87bsrcs8a3.fsf@deneb.enyo.de...
> Robert A Duff <bobduff@world.std.com> 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.