search for: pointerid

...same loopid (the self-referencing id metadata from the llvm.loop.parallel patch), check their iteration identifier, and if it's different, return NO ALIAS. The similar idea could be applied to preserve the 'restrict' info across function inlines: llvm.mem.restricted_access [funcid] [pointerid] Similarly, if the RestrictedPointerAA finds that both of the accesses are marked with this metadata and point to the same funcid, and the [pointerid] is different, it can return NO ALIAS. -- Pekka

...p.parallel patch), check their iteration identifier, and if > it's > different, return NO ALIAS. This also makes sense. > > The similar idea could be applied to preserve the 'restrict' info > across > function inlines: > > llvm.mem.restricted_access [funcid] [pointerid] > > Similarly, if the RestrictedPointerAA finds that both of the accesses > are > marked with this metadata and point to the same funcid, and the > [pointerid] > is different, it can return NO ALIAS. Interesting idea. I had worked out a proposal for more-general restrict suppor...

----- Original Message ----- > From: "Andrew Trick" <atrick at apple.com> > To: "Tobias Grosser" <tobias at grosser.es> > Cc: "llvmdev at cs.uiuc.edu Dev" <llvmdev at cs.uiuc.edu> > Sent: Sunday, February 17, 2013 2:32:25 PM > Subject: Re: [LLVMdev] Parallel Loop Metadata > > > > > > On Feb 11, 2013, at 2:58 PM,

On Feb 11, 2013, at 2:58 PM, Tobias Grosser <tobias at grosser.es> wrote: > On 02/11/2013 10:31 PM, Nadav Rotem wrote: >> Now that we have a better understanding of the proposal for using per-instruction metadata, I think that we need to revisit the "single metedata" approach (Pekka's original suggestion). > > Following Andrew's comments we understood that