macro LFDS700_PAL_ATOMIC_DWCAS
Source File
└───liblfds700
└───inc
└───liblfds700
lfds700_misc.h
lfds700_porting_abstraction_layer_compiler.h
Enums
enum lfds700_misc_cas_strength { LFDS700_MISC_CAS_WEAK, LFDS700_MISC_CAS_STRONG };
Macro
#define LFDS700_PAL_ATOMIC_DWCAS( pointer_to_destination, pointer_to_compare, pointer_to_new_destination, cas_strength, result ) [compiler atomic DWCAS instrinsic]
Parameters
pointer_to_destination
- A pointer to an array of two lfds700_pal_atom_t volatile. The value of *pointer_to_destination is compared to the value of *pointer_to_compare and if they are equal, *new_value is written into *pointer_to_destination.
pointer_to_compare
- A pointer to an array of two lfds700_pal_atom_t. Whether or not the compare is successful (and so whether or not *new_value is written into *pointer_to_destination), the original value of *pointer_to_destination is written into *pointer_to_compare, i.e. the compare value is always lost.
pointer_to_new_destination
- A pointer to an array of two lfds700_pal_atom_t. This value is written into *pointer_to_destination if *pointer_to_destination and *pointer_to_compare are equal.
cas_strength
- This argument is only meaningful on LL/SC platforms, and if set to LFDS700_MISC_CAS_STRONG indicates the macro should internally retry if the LL/SC operation aborted. See Notes.
result
- A char unsigned, which is set to 1 if the swap occurred, 0 if not.
Return Value
No return value.
Example
#define LFDS700_PAL_ATOMIC_DWCAS( pointer_to_destination, pointer_to_compare, pointer_to_new_destination, cas_strength, result ) \
{ \
(result) = 0; \
\
__asm__ __volatile__ \
( \
"lock;" /* make cmpxchg16b atomic */ \
"cmpxchg16b %0;" /* cmpxchg16b sets ZF on success */ \
"setz %3;" /* if ZF set, set result to 1 */ \
\
/* output */ \
: "+m" (*pointer_to_destination), "+a" ((pointer_to_compare)[0]), "+d" ((pointer_to_compare)[1]), "=q" (result) \
\
/* input */ \
: "b" ((pointer_to_new_destination)[0]), "c" ((pointer_to_new_destination)[1]) \
\
/* clobbered */ \
: "cc", "memory" \
); \
}
Optionality
This macro is optional. If it is not given, the macro must be absent, rather than empty.
Notes
All of the atomic operation macros open and close with curley braces as some of them need to declare variables on the stack, so that they can operate in ways which match their 'prototype' (i.e. they may need a bit of temporary storage, as the way in which the macro is arranged to work doesn't map directly to the atomic intrinsic prototype for that platform). We see this here in the example.
The actual atomic intrinsic if it does not inherently provide compiler barriers itself MUST be immediately preceeded and followed by LFDS700_PAL_BARRIER_COMPILER_FULL. This is to prevent compiler re-ordering.
Finally, we get to the actual atomic operation itself. The liblfds700_pal_atom_t types need to be cast to the types the intrinsic expects, and to the maximum extent possible eschew any memory barriers. On ARM, for example, memory barriers and atomic operations are wholly seperated and on that platform, the operation is and is only an atomic operation. The data structures themselves issue memory barriers as and when they must, and any additional barriers issued within the atomic macros are only overhead. On x86 and x64, sadly, memory barriers are built into the atomic operations and cannot be removed. On Itanium, it looks like atomic operations must occur with a barrier, but it is possible to choose a load, store or full barrier, and as such on that platform, the load barrier is always used, as it is the lowest cost of the three.
The example here is for a platform (x64 GCC) where the processor supports DWCAS, but where the compiler has no intrinsic for this operation. As such, it is necessary to directly issue the necessary assembly instructions.
If this atomic operaton is not available, the macro must be left undefined, which will lead to a placeholder version automatically being used. This placeholder version if called first calls LFDS700_PAL_ASSERT and then, assuming execution has continued (i.e. LFDS700_PAL_ASSERT is not defined, or is defined but this is a release user-mode build and so asserts are not being checked) will attempt to write 0 into memory location 0, to deliberately crash.