Home
last modified time | relevance | path

Searched refs:ACQUIRE (Results 1 – 5 of 5) sorted by relevance

/external/google-benchmark/src/
Dmutex.h37 #define ACQUIRE(...) \ macro
79 void lock() ACQUIRE() { mut_.lock(); } in lock()
91 MutexLock(Mutex& m) ACQUIRE(m) : ml_(m.native_handle()) {} in MutexLock()
/external/libcxx/utils/google-benchmark/src/
Dmutex.h37 #define ACQUIRE(...) \ macro
79 void lock() ACQUIRE() { mut_.lock(); } in lock()
91 MutexLock(Mutex& m) ACQUIRE(m) : ml_(m.native_handle()) {} in MutexLock()
/external/clang/docs/
DThreadSafetyAnalysis.rst79 as such (using ``ACQUIRE``/``RELEASE``).
212 ACQUIRE(...), ACQUIRE_SHARED(...), RELEASE(...), RELEASE_SHARED(...)
218 ``ACQUIRE`` is an attribute on functions or methods, which
233 void lockAndInit() ACQUIRE(mu) {
249 If no argument is passed to ``ACQUIRE`` or ``RELEASE``, then the argument is
264 void Lock() ACQUIRE() { mu.Lock(); }
415 as ``ACQUIRE``. See :ref:`mutexheader`, below, for example uses.
718 ~MutexUnlocker() ACQUIRE(mu) { mu->Lock(); }
793 #define ACQUIRE(...) \
834 void Lock() ACQUIRE();
[all …]
/external/tensorflow/tensorflow/core/platform/default/
Dthread_annotations.h76 #define ACQUIRE(...) \ macro
/external/ipsec-tools/src/racoon/
DTODO25 ACQUIRE message.
104 to do this, we need to remember which ACQUIRE was caused by which socket,