Displaying 4 results from an estimated 4 matches for "synchronizationscop".
Did you mean:
synchronizationscope
2014 Mar 07
3
[LLVMdev] [RFC] Add second "failure" AtomicOrdering to cmpxchg instruction
...SDValue Ptr, SDValue Cmp, SDValue Swp,
MachinePointerInfo PtrInfo, unsigned Alignment,
- AtomicOrdering Ordering,
+ AtomicOrdering SuccessOrdering,
+ AtomicOrdering FailureOrdering,
SynchronizationScope SynchScope);
SDValue getAtomic(unsigned Opcode, SDLoc dl, EVT MemVT, SDValue Chain,
SDValue Ptr, SDValue Cmp, SDValue Swp,
MachineMemOperand *MMO,
- AtomicOrdering Ordering,
+ AtomicOrdering SuccessOrdering,
+...
2014 Dec 11
2
[LLVMdev] [RFC][PATCH][OPENCL] synchronization scopes redux
...U in bitcode).
4. New syntax "synchscope(n)" for other scopes.
5. There is no keyword for cross-thread, but it can be specified as
"synchscope(0)".
This change breaks forward compatibility for the bitcode, since the
meaning of the zero/one values are now changed.
enum SynchronizationScope {
- SingleThread = 0,
- CrossThread = 1
+ CrossThread = 0,
+ SingleThread = ~0U
};
The change passes almost all lit tests including one new test (see patch
0005). The failing tests are specifically checking for forward
compatibility:
Failing Tests (3):
LLVM :: Bitcode/cmpxchg-upgrad...
2013 Aug 23
1
[LLVMdev] Incredible effects of extending AtomicSDNode::Ops
...Even this innocuous change:
====================
--- a/include/llvm/CodeGen/SelectionDAGNodes.h
+++ b/include/llvm/CodeGen/SelectionDAGNodes.h
@@ -1068,6 +1068,7 @@ public:
///
class AtomicSDNode : public MemSDNode {
SDUse Ops[4];
+ SDUse buffer;
void InitAtomic(AtomicOrdering Ordering, SynchronizationScope SynchScope) {
// This must match encodeMemSDNodeFlags() in SelectionDAG.cpp.
====================
-- makes LLVM fail 83 regression tests, basically everything related
to the atomic ops, in a bunch of unrelated ways: some segfaults, some
failing assertions, some wrong outputs, all suggesting...
2014 Dec 24
2
[LLVMdev] [RFC][PATCH][OPENCL] synchronization scopes redux
...uot;synchscope(n)" for other scopes.
> 5. There is no keyword for cross-thread, but it can be specified as
> "synchscope(0)".
>
> This change breaks forward compatibility for the bitcode, since the
> meaning of the zero/one values are now changed.
>
> enum SynchronizationScope {
> - SingleThread = 0,
> - CrossThread = 1
> + CrossThread = 0,
> + SingleThread = ~0U
> };
>
> The change passes almost all lit tests including one new test (see patch
> 0005). The failing tests are specifically checking for forward
> compatibility:
>
> Fail...