Displaying 3 results from an estimated 3 matches for "6eed7a7e".
2013 Feb 05
0
[LLVMdev] Vectorizing global struct pointers
On Feb 5, 2013, at 9:22 AM, Hal Finkel <hfinkel at anl.gov> wrote:
> I think that the potential for overlap is indeed there, but don't we already insert runtime overlap checks as necessary? This seems like it would just be another such case.
We insert runtime overlap checks only for unidentified objects. The problem here is that the vectorizer thinks that A,B,C are all pointers to
2013 Feb 05
1
[LLVMdev] Vectorizing global struct pointers
...ks. ;)
I'll try to inspect the uses for GEPs and store the offsets in a map. If it
works, we can think of a better implementation.
cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130205/6eed7a7e/attachment.html>
2013 Feb 05
3
[LLVMdev] Vectorizing global struct pointers
----- Arnold Schwaighofer <aschwaighofer at apple.com> wrote:
> If I understand you correctly, conceptually you want two different objects to be returned for Foo.bl and Foo.al?
>
> Here is my take on this (take this with a grain of salt, Dan is the expert on this):
>
> http://llvm.org/docs/GetElementPtr.html#what-happens-if-an-array-index-is-out-of-bounds
>
>