Displaying 2 results from an estimated 2 matches for "d20665".
2017 Aug 20
5
RFC: Resolving TBAA issues
>
>
>
> I do not believe the current proposal will solve all of those cases,
> particularly when the fields are the same type and structures are
> compatible but they cannot overlap in C/C++ anyway.
>
> One of the threads is titled "[PATCH] D20665: Claim NoAlias if two GEPs
index different fields of the same struct"
For example, given
struct {
int arr_a[2];
int arr_b[2];
};
assume you cannot see the original allocation site.
in llvm ir gep(arr_b, -1) is legally an access to arr_a[1].
You can use -1 even though it's going to be...
2017 Aug 20
3
RFC: Resolving TBAA issues
On 08/20/2017 11:22 AM, Daniel Berlin via llvm-dev wrote:
> Sorry, hit send early.
>
>
> On Sun, Aug 20, 2017 at 9:16 AM, Daniel Berlin <dberlin at dberlin.org
> <mailto:dberlin at dberlin.org>> wrote:
>
>
>
> On Sun, Aug 20, 2017 at 8:54 AM, Ivan A. Kosarev via llvm-dev
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at