Lines Matching refs:held
113 capability can be held by only one thread at a time, while a shared capability
114 can be held by many threads at the same time. This mechanism enforces a
128 The set of capabilities that are actually held by a given thread at a given
132 and describes the set of capabilities that are statically known to be held, or
133 not held, at that particular point. This environment is a conservative
134 approximation of the full set of capabilities that will actually held by a
190 must be held on entry to the function, *and must still be held on exit*.
425 to fail (no return) if the capability is not held. See :ref:`mutexheader`,
465 ensuring that a capability is held before reading or writing to guarded data,
467 *not* held.
507 should *not* be held.
635 No conditionally held locks.
638 The analysis must be able to determine whether a lock is held, or not held, at
639 every program point. Thus, sections of code where a lock *might be held* will
647 ... // Warning! Mutex 'mu' is not held on every path through here.
855 // Assert that this mutex is currently held by the calling thread.
858 // Assert that is mutex is currently held for read operations.