search for: 008323

...type is passed by-copy (= > > by-value) > > for alias analysis purposes, while actually passing it by-reference > > (= via a pointer). > > I'm not sure, but based on Chris's suggested implementation > > http://lists.cs.uiuc.edu/pipermail/llvmdev/2007-March/008323.html > > it seems that this may map exactly to "noalias". There is a subtlety > > though: the compiler may pretend that a copy was passed in, but it > > must > > correspond to a copy made at the moment of the function call, not > > later. > > >...

...the compiler to pretend that a formal argument of that type is passed by-copy (= by-value) for alias analysis purposes, while actually passing it by-reference (= via a pointer). I'm not sure, but based on Chris's suggested implementation http://lists.cs.uiuc.edu/pipermail/llvmdev/2007-March/008323.html it seems that this may map exactly to "noalias". There is a subtlety though: the compiler may pretend that a copy was passed in, but it must correspond to a copy made at the moment of the function call, not later. In Chris's description " The semantics of 'noalias'...

...a formal argument of that type is passed by-copy (= > by-value) > for alias analysis purposes, while actually passing it by-reference > (= via a pointer). > I'm not sure, but based on Chris's suggested implementation > http://lists.cs.uiuc.edu/pipermail/llvmdev/2007-March/008323.html > it seems that this may map exactly to "noalias". There is a subtlety > though: the compiler may pretend that a copy was passed in, but it > must > correspond to a copy made at the moment of the function call, not > later. > > In Chris's description &gt...

On Aug 19, 2007, at 1:15 PM, Gordon Henriksen wrote: > On 2007-08-19, at 15:41, Duncan Sands wrote: > >> can you please explain more about what restrict means: it may help >> in improving code quality for Ada. In Ada you have runtime >> constants that are really constant, for example array bounds. The >> bounds are passed around by pointer, which causes LLVM