mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-12-20 09:30:43 +00:00
211ffd242d
I've managed to convince myself that AArch64's acquire/release instructions are sufficient to guarantee C++11's required semantics, even in the sequentially-consistent case. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@179005 91177308-0d34-0410-b5e6-96231b3b80d8
27 lines
833 B
LLVM
27 lines
833 B
LLVM
; RUN: llc -mtriple=aarch64-none-linux-gnu -verify-machineinstrs < %s | FileCheck %s
|
|
|
|
define i32 @foo(i32* %var, i1 %cond) {
|
|
; CHECK: foo:
|
|
br i1 %cond, label %atomic_ver, label %simple_ver
|
|
simple_ver:
|
|
%oldval = load i32* %var
|
|
%newval = add nsw i32 %oldval, -1
|
|
store i32 %newval, i32* %var
|
|
br label %somewhere
|
|
atomic_ver:
|
|
fence seq_cst
|
|
%val = atomicrmw add i32* %var, i32 -1 monotonic
|
|
fence seq_cst
|
|
br label %somewhere
|
|
; CHECK: dmb
|
|
; CHECK: ldxr
|
|
; CHECK: dmb
|
|
; The key point here is that the second dmb isn't immediately followed by the
|
|
; simple_ver basic block, which LLVM attempted to do when DMB had been marked
|
|
; with isBarrier. For now, look for something that looks like "somewhere".
|
|
; CHECK-NEXT: mov
|
|
somewhere:
|
|
%combined = phi i32 [ %val, %atomic_ver ], [ %newval, %simple_ver]
|
|
ret i32 %combined
|
|
}
|