search for: istriviallydisjoint

I was lost from the thread at some point. Making the interface more general sounds good to me. This helps to solve Escha's concern 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 ----- > &...

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:...

...the interface more general sounds good to me. This helps to > > solve > > Escha's concern 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-...

On 08/07/2015 06:13 PM, Hal Finkel wrote: > But you seem to be implying that you'll use different address spaces > at the IR level, but that these address spaces will be changed prior > to the target seeing them? Or that the target will internally map them > all to address space 0 (instead of aborting). If the target knows to > do this mapping, it can also understand the