admin/mlib
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix incorrect qualifier position for emulation layer (issue for atomic pointer definition)

Browse Source
This commit is contained in:
Patrick Pelissier committed 2019-01-02 22:15:47 +01:00
1 parent 38eb1c26c6
commit 60f1454550
1 file changed
+5 -5
Download Patch File Download Diff File Expand all files Collapse all files
m-atomic.h
+5 -5
View File
@@ -98,7 +98,7 @@ using std::memory_order_seq_cst;
#define _Atomic(T) std::atomic< T > #define _Atomic(T) std::atomic< T >
#elif (defined(__STDC_VERSION__) && __STDC_VERSION__ >= 201112L) \ #elif (defined(__STDC_VERSION__) && __STDC_VERSION__ >= 201112L) \
|| ( defined(__GNUC__) && !defined(__clang__) && !defined(__cplusplus) && (__GNUC__*100 + __GNUC_MINOR__) >= 409) \ || ( defined(__GNUC__) && !defined(__clang__) && !defined(__cplusplus) && (__GNUC__*100 + __GNUC_MINOR__) >= 409) \
|| (defined(__clang__) && __clang_major__ >= 4) || (defined(__clang__) && __clang_major__ >= 4)
@@ -125,10 +125,10 @@ using std::memory_order_seq_cst;
*/ */
#define _Atomic(T) \ #define _Atomic(T) \
struct { \ struct { \
volatile T _val; \ T volatile _val; \
T _zero; \ T _zero; \
T _previous; \ T _previous; \
m_mutex_t _lock; \ m_mutex_t _lock; \
} }
/* Even if memory order is defined, only the strongest constraint is used */ /* Even if memory order is defined, only the strongest constraint is used */