search for: unmodified

...actually, you have a number of problems if you attach noalias to GEP's. >From C99 (6.7.3.1, example 3): " The function parameter declarations void h(int n, int * restrict p, int * restrict q, int * restrict r) { int i; for (i = 0; i < n; i++) p[i] = q[i] + r[i]; } illustrate how an unmodified object can be aliased through two restricted pointers. In particular, if a and b are disjoint arrays, a call of the form h(100, a, b, b) has defined behavior, because array b is not modified within function h. " If you claim q and r (which may or may not share a GEP) noalias each other, that...

...> to GEP's. > From C99 (6.7.3.1, example 3): > " > > The function parameter declarations > > void h(int n, int * restrict p, int * restrict q, int * restrict r) > { > int i; > for (i = 0; i < n; i++) > p[i] = q[i] + r[i]; > } > illustrate how an unmodified object can be aliased through two > restricted pointers. In particular, if a and b > are disjoint arrays, a call of the form h(100, a, b, b) has defined > behavior, because array b is not > modified within function h. > " > > If you claim q and r (which may or may not sh...

..., example 3): >> " >> >> The function parameter declarations >> >> void h(int n, int * restrict p, int * restrict q, int * restrict r) >> { >> int i; >> for (i = 0; i < n; i++) >> p[i] = q[i] + r[i]; >> } >> illustrate how an unmodified object can be aliased through two >> restricted pointers. In particular, if a and b >> are disjoint arrays, a call of the form h(100, a, b, b) has defined >> behavior, because array b is not >> modified within function h. >> " >> >> If you claim q and...

----- Original Message ----- > From: "Chandler Carruth" <chandlerc at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, "Clang Developers" <cfe-dev at cs.uiuc.edu>, "Dan Gohman" > <dan433584 at gmail.com> > Sent: Sunday, December 2, 2012

...nction parameter declarations > >> > >> void h(int n, int * restrict p, int * restrict q, int * restrict > >> r) > >> { > >> int i; > >> for (i = 0; i < n; i++) > >> p[i] = q[i] + r[i]; > >> } > >> illustrate how an unmodified object can be aliased through two > >> restricted pointers. In particular, if a and b > >> are disjoint arrays, a call of the form h(100, a, b, b) has defined > >> behavior, because array b is not > >> modified within function h. > >> " > >&g...

Hi Daniel, On Aug 24, 2007, at 10:20 AM, Daniel Berlin wrote: > On 8/22/07, Christopher Lamb <christopher.lamb at gmail.com> wrote: >> >> >> On Aug 22, 2007, at 3:48 PM, Duncan Sands wrote: >> >> Hi Christopher, >> >> >> If A and B are function arguments then there is no "based on" >> relationship between pointer

...t; >> >> >> void h(int n, int * restrict p, int * restrict q, int * restrict >> >> r) >> >> { >> >> int i; >> >> for (i = 0; i < n; i++) >> >> p[i] = q[i] + r[i]; >> >> } >> >> illustrate how an unmodified object can be aliased through two >> >> restricted pointers. In particular, if a and b >> >> are disjoint arrays, a call of the form h(100, a, b, b) has defined >> >> behavior, because array b is not >> >> modified within function h. >> >&gt...

...p, int * restrict q, int * > >> >> restrict > >> >> r) > >> >> { > >> >> int i; > >> >> for (i = 0; i < n; i++) > >> >> p[i] = q[i] + r[i]; > >> >> } > >> >> illustrate how an unmodified object can be aliased through two > >> >> restricted pointers. In particular, if a and b > >> >> are disjoint arrays, a call of the form h(100, a, b, b) has > >> >> defined > >> >> behavior, because array b is not > >> >>...