search for: 064620

...e alias analysis that > treats pointers in different address spaces not aliasing. This patch got > shot down because, in some targets, address spaces may alias. For example, > in CUDA+NVPTX, addrspace(0) aliases everyone. > > (2) http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-August/064620.html. > Michele Scandale proposed address space extensions in IR metadata which > TBAA could then leverage to prove non-aliasing. This approach didn't fly > either because address spaces are target-specific. The front end doesn't > know enough to decide aliasing. > > So, c...

...t >> treats pointers in different address spaces not aliasing. This patch got >> shot down because, in some targets, address spaces may alias. For example, >> in CUDA+NVPTX, addrspace(0) aliases everyone. >> >> (2) http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-August/064620.html. >> Michele Scandale proposed address space extensions in IR metadata which >> TBAA could then leverage to prove non-aliasing. This approach didn't fly >> either because address spaces are target-specific. The front end doesn't >> know enough to decide aliasing....

...d to add an address-space alias analysis that treats pointers in different address spaces not aliasing. This patch got shot down because, in some targets, address spaces may alias. For example, in CUDA+NVPTX, addrspace(0) aliases everyone. (2) http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-August/064620.html. Michele Scandale proposed address space extensions in IR metadata which TBAA could then leverage to prove non-aliasing. This approach didn't fly either because address spaces are target-specific. The front end doesn't know enough to decide aliasing. So, can we make BasicAA to conside...