IR: add "cmpxchg weak" variant to support permitted failure.
This commit adds a weak variant of the cmpxchg operation, as described
in C++11. A cmpxchg instruction with this modifier is permitted to
fail to store, even if the comparison indicated it should.
As a result, cmpxchg instructions must return a flag indicating
success in addition to their original iN value loaded. Thus, for
uniformity *all* cmpxchg instructions now return "{ iN, i1 }". The
second flag is 1 when the store succeeded.
At the DAG level, a new ATOMIC_CMP_SWAP_WITH_SUCCESS node has been
added as the natural representation for the new cmpxchg instructions.
It is a strong cmpxchg.
By default this gets Expanded to the existing ATOMIC_CMP_SWAP during
Legalization, so existing backends should see no change in behaviour.
If they wish to deal with the enhanced node instead, they can call
setOperationAction on it. Beware: as a node with 2 results, it cannot
be selected from TableGen.
Currently, no use is made of the extra information provided in this
patch. Test updates are almost entirely adapting the input IR to the
new scheme.
Summary for out of tree users:
------------------------------
+ Legacy Bitcode files are upgraded during read.
+ Legacy assembly IR files will be invalid.
+ Front-ends must adapt to different type for "cmpxchg".
+ Backends should be unaffected by default.
llvm-svn: 210903
2014-06-13 16:24:07 +02:00
|
|
|
; RUN: llvm-as %s -o - | llvm-dis | FileCheck %s
|
2014-08-19 23:08:27 +02:00
|
|
|
; RUN: verify-uselistorder < %s
|
IR: add "cmpxchg weak" variant to support permitted failure.
This commit adds a weak variant of the cmpxchg operation, as described
in C++11. A cmpxchg instruction with this modifier is permitted to
fail to store, even if the comparison indicated it should.
As a result, cmpxchg instructions must return a flag indicating
success in addition to their original iN value loaded. Thus, for
uniformity *all* cmpxchg instructions now return "{ iN, i1 }". The
second flag is 1 when the store succeeded.
At the DAG level, a new ATOMIC_CMP_SWAP_WITH_SUCCESS node has been
added as the natural representation for the new cmpxchg instructions.
It is a strong cmpxchg.
By default this gets Expanded to the existing ATOMIC_CMP_SWAP during
Legalization, so existing backends should see no change in behaviour.
If they wish to deal with the enhanced node instead, they can call
setOperationAction on it. Beware: as a node with 2 results, it cannot
be selected from TableGen.
Currently, no use is made of the extra information provided in this
patch. Test updates are almost entirely adapting the input IR to the
new scheme.
Summary for out of tree users:
------------------------------
+ Legacy Bitcode files are upgraded during read.
+ Legacy assembly IR files will be invalid.
+ Front-ends must adapt to different type for "cmpxchg".
+ Backends should be unaffected by default.
llvm-svn: 210903
2014-06-13 16:24:07 +02:00
|
|
|
|
|
|
|
|
define void @test_cmpxchg(i32* %addr, i32 %desired, i32 %new) {
|
|
|
|
|
cmpxchg i32* %addr, i32 %desired, i32 %new seq_cst seq_cst
|
|
|
|
|
; CHECK: cmpxchg i32* %addr, i32 %desired, i32 %new seq_cst seq_cst
|
|
|
|
|
|
|
|
|
|
cmpxchg volatile i32* %addr, i32 %desired, i32 %new seq_cst monotonic
|
|
|
|
|
; CHECK: cmpxchg volatile i32* %addr, i32 %desired, i32 %new seq_cst monotonic
|
|
|
|
|
|
|
|
|
|
cmpxchg weak i32* %addr, i32 %desired, i32 %new acq_rel acquire
|
|
|
|
|
; CHECK: cmpxchg weak i32* %addr, i32 %desired, i32 %new acq_rel acquire
|
|
|
|
|
|
|
|
|
|
cmpxchg weak volatile i32* %addr, i32 %desired, i32 %new singlethread release monotonic
|
|
|
|
|
; CHECK: cmpxchg weak volatile i32* %addr, i32 %desired, i32 %new singlethread release monotonic
|
|
|
|
|
|
|
|
|
|
ret void
|
2014-07-29 03:10:57 +02:00
|
|
|
}
|
