3a72496b5c
C++20 deprecated compound volatile statements such as pre- and post-increments, to stress that they're not atomic. So instead of volatile i; ~~~~; ++i; you're now supposed to write volatile i; ~~~~; int j = i; // volatile load ++j; i = j; // volatile store which matches more closely what hardware does. Instead of fixing every use of volatile pre- or post-increment in this fashion individually, and realising that probably a few more Qt modules will have the same kind of code patterns in them, write QtPrivate functions to do the job centrally. Change-Id: I838097bd484ef2118c071726963f103c080d2ba5 Reviewed-by: Lars Knoll <lars.knoll@qt.io> |
||
---|---|---|
.. | ||
qatomicint | ||
qatomicinteger | ||
qatomicpointer | ||
qfuture | ||
qfuturesynchronizer | ||
qfuturewatcher | ||
qmutex | ||
qmutexlocker | ||
qpromise | ||
qreadlocker | ||
qreadwritelock | ||
qresultstore | ||
qsemaphore | ||
qthread | ||
qthreadonce | ||
qthreadpool | ||
qthreadstorage | ||
qwaitcondition | ||
qwritelocker | ||
CMakeLists.txt |