search for: addressspacealia

...embedding alias info in >> TargetData. Now that we have TTI, it seems a better place to hold >> target-specific alias info than DataLayout. >> >> Any comments? >> >> Jingyue >> > > We definitely need something to handle this. > > I think a TTI::addressSpaceAlias is a good idea, although I don't think > this fully solves the language vs. target address space distinction a > metadata based approach was supposed to handle although it would be easier > to implement. For our GPU purposes this would mostly be enough. For > example, the fact that...

...get-defined way. Actually, John Criswell did mention in that thread the idea of embedding alias info in TargetData. Now that we have TTI, it seems a better place to hold target-specific alias info than DataLayout. Any comments? Jingyue We definitely need something to handle this. I think a TTI::addressSpaceAlias is a good idea, although I don't think this fully solves the language vs. target address space distinction a metadata based approach was supposed to handle although it would be easier to implement. For our GPU purposes this would mostly be enough. For example, the fact that in OpenCL local vs....

+ the new llvm-dev On Fri, Aug 7, 2015 at 11:30 AM, Jingyue Wu <jingyue at google.com> wrote: > Hi folks, > > Unsurprisingly, leveraging the fact that certain address spaces don't > alias can significantly improve alias analysis precision and enhance > (observably 2x performance gain) load/store optimizations such as LICM and > DSE. > > This sounds to me an