search for: pursuring

...r the function. > All in all, I would prefer the stronger guarantee of the readonly > attribute (that the memory location is unchanged, regardless of > through which pointer it is accessed). Perhaps this is indeed the only strategy that is completely self-consistent. I don't object to pursuring this. > > As I said earlier, the original problem highlighted by Reid's > > example > > cannot currently occur: that could only happen if you remove the > > @llvm.assume call (thus making the other argument unused). We > > already don't do this (because the a...

...efer the stronger guarantee of the readonly >> attribute (that the memory location is unchanged, regardless of through >> which pointer it is accessed). >> >> >> Perhaps this is indeed the only strategy that is completely >> self-consistent. I don't object to pursuring this. >> >> >> >>> >>> As I said earlier, the original problem highlighted by Reid's example >>> cannot currently occur: that could only happen if you remove the >>> @llvm.assume call (thus making the other argument unused). We already don...

----- Original Message ----- > From: "Chandler Carruth" <chandlerc at google.com> > To: "Hal Finkel" <hfinkel at anl.gov>, "Sanjoy Das" <sanjoy at playingwithpointers.com> > Cc: "cfe-dev at cs.uiuc.edu Developers" <cfe-dev at cs.uiuc.edu>, "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: