[LLVMdev] Intended semantics for ``fence seq_cst``

JF Bastien jfb at google.com
Wed Jul 31 18:39:07 PDT 2013

> You will need to do this in the frontend. The target independent
optimizers are allowed to use the memory model.

We discussed doing this, and concluded that doing it pre-opt was overly
restrictive on correct code. Doing it post-opt bakes the behavior into the
portable code, so in a way it'll be reliably broken but won't penalize good

FWIW it's easy to change from one to the other: move one line of code. I
hope my explanation makes sense, and it doesn't look like I'm dismissing
your comment on implementation issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130731/fdd46a7c/attachment.html>

More information about the llvm-dev mailing list