Displaying 4 results from an estimated 4 matches for "noliass".
Did you mean:
noaliass
2020 Jun 21
3
Restrict qualifier on class members
....at(i);
26 }
27
28 return 0;
29 }
It's given that pointer a, in each object of the class RemotePtr, is the
only pointer that can access the array pointed by it. So, I tried __remote
int* __restrict a; (line 9) construct to tell Clang the same. This doesn't
seem to work and I see no noliass in the generated IR. Specifically, I want
lines 23-26 optimized assuming no aliasing between A and B. Any reason why
Clang shouldn't annotate memory accesses in lines 23-26 with noaliass
taking line 9 into account?
The higher level problem is this: is there a way to compile lines 23-26
assumin...
2020 Jun 22
2
Restrict qualifier on class members
...urn 0;
> 29 }
>
> It's given that pointer a, in each object of the class RemotePtr, is the
> only pointer that can access the array pointed by it. So, I tried __remote
> int* __restrict a; (line 9) construct to tell Clang the same. This doesn't
> seem to work and I see no noliass in the generated IR. Specifically, I want
> lines 23-26 optimized assuming no aliasing between A and B. Any reason why
> Clang shouldn't annotate memory accesses in lines 23-26 with noaliass
> taking line 9 into account?
>
> The higher level problem is this: is there a way to com...
2020 Jun 22
2
Restrict qualifier on class members
...at pointer a, in each object of the class RemotePtr, is the
>> > only pointer that can access the array pointed by it. So, I tried
>> __remote
>> > int* __restrict a; (line 9) construct to tell Clang the same. This
>> doesn't
>> > seem to work and I see no noliass in the generated IR. Specifically, I
>> want
>> > lines 23-26 optimized assuming no aliasing between A and B. Any reason
>> why
>> > Clang shouldn't annotate memory accesses in lines 23-26 with noaliass
>> > taking line 9 into account?
>> >
>&g...
2020 Jun 24
2
FW: Restrict qualifier on class members
...t; It's given that pointer a, in each object of the class RemotePtr, is the
> > only pointer that can access the array pointed by it. So, I tried
> __remote
> > int* __restrict a; (line 9) construct to tell Clang the same. This
> doesn't
> > seem to work and I see no noliass in the generated IR. Specifically, I
> want
> > lines 23-26 optimized assuming no aliasing between A and B. Any reason
> why
> > Clang shouldn't annotate memory accesses in lines 23-26 with noaliass
> > taking line 9 into account?
> >
> > The higher level pro...