search for: targetawarealiasanalysis

...rn that targets can know more about aliasing than just comparing address spaces. If there are no objections, I'll 1) add a new interface to TTI such as isTriviallyDisjoint. It returns false by default. 2) create a new AA that checks this interface, and add it to the AA chain. It could be named TargetAwareAliasAnalysis. Jingyue On Sun, Aug 9, 2015 at 2:34 PM, Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > ----- Original Message ----- > > From: "escha" <escha at apple.com> > > To: "Hal Finkel" <hfinkel at anl.gov> > > Cc: "Matt Arse...

.... > > > > If there are no objections, I'll > > 1) add a new interface to TTI such as isTriviallyDisjoint. It > > returns false > > by default. > > 2) create a new AA that checks this interface, and add it to the AA > > chain. > > It could be named TargetAwareAliasAnalysis. > > > > Jingyue > > > > On Sun, Aug 9, 2015 at 2:34 PM, Hal Finkel via llvm-dev > > <llvm-dev at lists.llvm.org> wrote: > >> > >> ----- Original Message ----- > >> > From: "escha" <escha at apple.com> > >> &...

Personally I feel the most intuitive approach would be to have an equivalent of isTriviallyDisjoint for IR; we already have a model for how it would work, and it could be a TTI call. I’ve kind of wanted this for a while because there’s a lot of address-space-esque aliasing relationships that can’t be easily modeled on the IR level. For example (in our model), we have some constraints like this: