Displaying 2 results from an estimated 2 matches for "volatile_ptr".
2016 Jul 15
2
RFC: Strong GC References in LLVM
...ind. GCC models it as an extra
fake edge from the BB containing a noreturn call to the exit block of the
function, so that nothing sinks below it by accident.
I do not believe we do anything special here, so yes, it also has the same
general issue as may-throw.
> and "while(true) {
> *volatile_ptr = 42; }" too?
I can move non-volatile stores past volatile stores :)
Or did you mean something else?
> Both of these are optimization barriers
> while still being "nounwind" (i.e. could be legitimately contained in
> a nounwind function); though not in exactly the sa...
2016 Jul 15
3
RFC: Strong GC References in LLVM
On Fri, Jul 15, 2016 at 12:21 PM, Sanjoy Das <sanjoy at playingwithpointers.com
> wrote:
> Hi Daniel,
>
> Daniel Berlin wrote:
> > As a starting point, LLVM will conservatively not speculate such
> > loads and stores; and will leave open the potential to upstream
> > logic that will have a more precise sense of when these loads
> and