search for: assert_immut

...vm.safe_cast is, as you note, stores to the pointer passed to safe_cast will not be forwarded to loads from the pointer it returns. I think this issue can be solved by modeling `llvm.safe_cast` not as a transformation on a pointer, but as a check. Specifically, I imagine a readonly intrinsic `llvm.assert_immutable` that "asserts" that the pointer passed to it is immutable, and unwinds if that fact isn't true (these are only imaginary semantics -- we know the intrinsic will never actually unwind). This means `llvm.assert_immutable` can't be marked nounwind (otherwise it would just get o...

On 09/28/2014 01:22 AM, Hal Finkel wrote: > ----- Original Message ----- >> From: "Philip Reames" <listmail at philipreames.com> >> To: llvmdev at cs.uiuc.edu >> Cc: "Hal Finkel" <hfinkel at anl.gov>, nicholas at mxc.ca >> Sent: Wednesday, September 10, 2014 12:11:28 AM >> Subject: Optimization hints for "constant" loads

On 10/21/2014 01:44 PM, Andrew Trick wrote: >> On Oct 21, 2014, at 11:46 AM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: >> >> Thank you for the explanation, I think I misunderstood your solution >> initially. Is it accurate to say: by making the definition of the >> source pointer of an !invariant load control (or data) dependent on >> some