Displaying 3 results from an estimated 3 matches for "hasaccesstoloopinvariantaddress".
2015 Mar 24
3
[LLVMdev] RFC: Loop versioning for LICM
> On Mar 20, 2015, at 8:02 PM, Nema, Ashutosh <Ashutosh.Nema at amd.com> wrote:
>
> > Yes, this is what I was proposing above and here ;):
> Thanks Adam it’s for confirming J
NP :).
>
> > No, not hasLoopInvariantStore but hasAccessToLoopInvariantAddress.
> Its only for invariant stores[not loads], Using ‘hasLoopInvariantStore’ (or a name with invariant store) makes more sense over ‘hasAccessToLoopInvariantAddress’.
Right but it’s the address that’s invariant not the store so hasLoopInvariantStore is a misleading name. How about hasStoreToLoop...
2015 Mar 20
2
[LLVMdev] RFC: Loop versioning for LICM
...onReport()
> 4010 << "write to a loop invariant address could not be vectorized");
> 4011 DEBUG(dbgs() << "LV: We don't allow storing to uniform addresses\n");
> 4012 return false;
> 4013 }
>
No, not hasLoopInvariantStore but hasAccessToLoopInvariantAddress.
You will also need to generate the memchecks for such accesses in canCheckPtrAtRT and addRuntimeCheck. Without those memchecks passing, the result of the dependence analysis is incorrect.
Adam
> Adam
>
> Regards,
> Ashutosh
-------------- next part --------------
An HTML attachm...
2015 Mar 19
2
[LLVMdev] RFC: Loop versioning for LICM
Hi Ashutosh,
> On Mar 16, 2015, at 9:06 PM, Nema, Ashutosh <Ashutosh.Nema at amd.com> wrote:
>
> Hi Adam,
>
> From: Adam Nemet [mailto:anemet at apple.com <mailto:anemet at apple.com>]
> Sent: Wednesday, March 11, 2015 10:48 AM
> To: Nema, Ashutosh
> Cc: llvmdev at cs.uiuc.edu <mailto:llvmdev at cs.uiuc.edu>
> Subject: Re: [LLVMdev] RFC: Loop