search for: 064594

...meter. The basic question ends up being if this is the intended behavior of noalias / restrict or just a bug. Here are 2 previous threads about attempts at fixing this problem: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-June/062895.html http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-August/064594.html Both of these I think sort of went in the wrong direction and talked specifically about the semantics of the atomic instructions (fence in particular), which isn't the real question. Is noalias supposed to mean that no other thread can also have a copy of the pointer it also modifies?...