search for: d4609

...t *x) { return foo(x+1, x); } You can't mark a and b as noalias here, even though NoAlias(x+1, x) == true. This is why I was saying that, unless the pointers come from distinct, identified underlying objects, you need to look at the uses of the pointers too. -Hal P.S. As discussed in D4609, we probably want to try adding CGSCC AA wrappers, to look back through function arguments, instead of using attribute propagation. > > Thanks > Hongbin > > On Thu, Nov 16, 2017 at 11:21 PM, Hal Finkel via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists....

...u can do this only for arguments with distinct (and identified) underlying objects (i.e., you need something a bit stronger than just "non-aliasing pointers"). -Hal On 11/16/2017 10:11 AM, via llvm-dev wrote: > Is this what you are looking for? > > https://reviews.llvm.org/D4609 > > Best, > > Haicheng Wu > > On 2017-11-14 20:34, Alexandre Isoard via llvm-dev wrote: >> Hello, >> >> Do we have a pass that propagate the noalias annotation down to the >> callee when: >> - it is static >> - it is always called with non alias...

...ark a and b as noalias here, even though NoAlias(x+1, > x) == true. This is why I was saying that, unless the pointers > come from distinct, identified underlying objects, you need to > look at the uses of the pointers too. > > -Hal > > P.S. As discussed in D4609, we probably want to try adding CGSCC > AA wrappers, to look back through function arguments, instead of > using attribute propagation. > > >> >> Thanks >> Hongbin >> >> On Thu, Nov 16, 2017 at 11:21 PM, Hal Finkel via llvm-dev >>...

Hello, Do we have a pass that propagate the noalias annotation down to the callee when: - it is static - it is always called with non aliasing pointers ? Or maybe that is incorrect? -- *Alexandre Isoard* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171114/ff86287c/attachment.html>

Hi, I am trying to get the alias info for the following code. The alias analysis returns "MayAlias" for arrays "A" and "B" in both the functions instead of "NoAlias". What passes should I run in opt before the alias analysis pass to get the accurate result? Example: //Note: static and called by func() only. static int sum(int *A, int *B) { int i = 0,

...e sense that they will "just contain" the implementation of a fixpoint data-flow analysis. The logic to determine/eliminate attributes will be similar to the one we have now. [0] https://reviews.llvm.org/D48387 [1] https://reviews.llvm.org/D50107 [2] https://reviews.llvm.org/D4609 [3] https://reviews.llvm.org/D50125 -- Johannes Doerfert PhD Student / Researcher Compiler Design Lab (Professor Hack) / Argonne National Laboratory Saarland Informatics Campus, Germany / Lemont, IL 60439, USA Building E1.3, Room 4.31 Tel. +49 (0)681 302-57521 : doerfert at cs.uni-saarland.de...