[LLVMdev] [RFC] Add compiler scheduling barriers
Tim Northover
t.p.northover at gmail.com
Thu Jul 3 04:52:10 PDT 2014
Hi Yi,
On 3 July 2014 12:04, Yi Kong <kongy.dev at gmail.com> wrote:
> After some internal discussions, we concluded that moving
> non-memory-access and non-side-effect instructions around memory
> barrier intrinsics is fine in almost any typical situation. In the
> rare occasions where reordering is undesirable, the programmer should
> use inline asm instead.
I'm curious now. What situations did you come up with where inline asm
would be needed?
Cheers.
Tim.
More information about the llvm-dev
mailing list