Displaying 5 results from an estimated 5 matches for "noaliass".
Did you mean:
noalias
2020 Jun 28
2
__restirct ignored when including headers like <cmath>
...int n) {
#pragma unroll 4
for(int i=0; i<n; ++i) {
a[i] += b[i];
}
}
results in:
; Function Attrs: nofree norecurse nounwind
define dso_local void @_Z7vec_addPiS_i(i32* noalias nocapture %a, i32*
noalias nocapture readonly %b, i32 %n) local_unnam
ed_addr #0 {
entry:
.
.
...
(note the noaliass before function arguments).
But this code:
#include <cmath>
void vec_add(int* __restrict a,
int* __restrict b,
int n) {
#pragma unroll 4
for(int i=0; i<n; ++i) {
a[i] += b[i];
}
}
results in:
; Function Attrs: nofree norecurse nounwind
define...
2020 Jun 21
3
Restrict qualifier on class members
...mote
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
assuming no aliasing between A and B, by just doing something in the
RemotePtr class (so that main is clear of ugly code)? If that's not
possible, is there a way to tell Clang that lines 23-26 s...
2020 Jun 22
2
Restrict qualifier on class members
...trict 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
> assuming no aliasing between A and B, by just doing something in the
> RemotePtr class (so that main is clear of ugly code)? If that's not
> possible, is there a way to...
2020 Jun 22
2
Restrict qualifier on class members
...is
>> 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
>> > assuming no aliasing between A and B, by just doing something in the
>> > RemotePtr class (so that main is clear of ugly code)? If tha...
2020 Jun 24
2
FW: Restrict qualifier on class members
...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
> > assuming no aliasing between A and B, by just doing something in the
> > RemotePtr class (so that main is clear of ugly code)? If that's not
> >...