Displaying 3 results from an estimated 3 matches for "addressspacesalias".
2015 Aug 07
6
[RFC] BasicAA considers address spaces?
...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 consider address spaces? Specifically, I am
> proposing:
> a) adding a new interface like TTI::addressSpacesAlias(unsigned,
> unsigned), and
> b) adding a little piece of logic in BasicAA that reports "no alias" if
> address spaces don't alias.
>
> This approach addresses the issue brought up in (2) because TTI can see
> the entire codegen. It also resolves the issue that shut d...
2015 Aug 07
2
[RFC] BasicAA considers address spaces?
...ach 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 consider address spaces? Specifically, I am
>> proposing:
>> a) adding a new interface like TTI::addressSpacesAlias(unsigned,
>> unsigned), and
>> b) adding a little piece of logic in BasicAA that reports "no alias" if
>> address spaces don't alias.
>>
>> This approach addresses the issue brought up in (2) because TTI can see
>> the entire codegen. It also resolv...
2015 Aug 08
2
[RFC] BasicAA considers address spaces?
...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 consider address spaces? Specifically, I am proposing:
a) adding a new interface like TTI::addressSpacesAlias(unsigned, unsigned), and
b) adding a little piece of logic in BasicAA that reports "no alias" if address spaces don't alias.
This approach addresses the issue brought up in (2) because TTI can see the entire codegen. It also resolves the issue that shut down (1) because it allows add...