| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279 | // Copyright 2017 The Abseil Authors.//// Licensed under the Apache License, Version 2.0 (the "License");// you may not use this file except in compliance with the License.// You may obtain a copy of the License at////      https://www.apache.org/licenses/LICENSE-2.0//// Unless required by applicable law or agreed to in writing, software// distributed under the License is distributed on an "AS IS" BASIS,// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.// See the License for the specific language governing permissions and// limitations under the License.//// -----------------------------------------------------------------------------// File: thread_annotations.h// -----------------------------------------------------------------------------//// This header file contains macro definitions for thread safety annotations// that allow developers to document the locking policies of multi-threaded// code. The annotations can also help program analysis tools to identify// potential thread safety issues.//// These annotations are implemented using compiler attributes. Using the macros// defined here instead of raw attributes allow for portability and future// compatibility.//// When referring to mutexes in the arguments of the attributes, you should// use variable names or more complex expressions (e.g. my_object->mutex_)// that evaluate to a concrete mutex object whenever possible. If the mutex// you want to refer to is not in scope, you may use a member pointer// (e.g. &MyClass::mutex_) to refer to a mutex in some (unknown) object.#ifndef ABSL_BASE_THREAD_ANNOTATIONS_H_#define ABSL_BASE_THREAD_ANNOTATIONS_H_// TODO(mbonadei): Remove after the backward compatibility period.#include "absl/base/internal/thread_annotations.h"  // IWYU pragma: export#if defined(__clang__)#define ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(x) __attribute__((x))#else#define ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(x)  // no-op#endif// ABSL_GUARDED_BY()//// Documents if a shared field or global variable needs to be protected by a// mutex. ABSL_GUARDED_BY() allows the user to specify a particular mutex that// should be held when accessing the annotated variable.//// Although this annotation (and ABSL_PT_GUARDED_BY, below) cannot be applied to// local variables, a local variable and its associated mutex can often be// combined into a small class or struct, thereby allowing the annotation.//// Example:////   class Foo {//     Mutex mu_;//     int p1_ ABSL_GUARDED_BY(mu_);//     ...//   };#define ABSL_GUARDED_BY(x) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(guarded_by(x))// ABSL_PT_GUARDED_BY()//// Documents if the memory location pointed to by a pointer should be guarded// by a mutex when dereferencing the pointer.//// Example://   class Foo {//     Mutex mu_;//     int *p1_ ABSL_PT_GUARDED_BY(mu_);//     ...//   };//// Note that a pointer variable to a shared memory location could itself be a// shared variable.//// Example:////   // `q_`, guarded by `mu1_`, points to a shared memory location that is//   // guarded by `mu2_`://   int *q_ ABSL_GUARDED_BY(mu1_) ABSL_PT_GUARDED_BY(mu2_);#define ABSL_PT_GUARDED_BY(x) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(pt_guarded_by(x))// ABSL_ACQUIRED_AFTER() / ABSL_ACQUIRED_BEFORE()//// Documents the acquisition order between locks that can be held// simultaneously by a thread. For any two locks that need to be annotated// to establish an acquisition order, only one of them needs the annotation.// (i.e. You don't have to annotate both locks with both ABSL_ACQUIRED_AFTER// and ABSL_ACQUIRED_BEFORE.)//// As with ABSL_GUARDED_BY, this is only applicable to mutexes that are shared// fields or global variables.//// Example:////   Mutex m1_;//   Mutex m2_ ABSL_ACQUIRED_AFTER(m1_);#define ABSL_ACQUIRED_AFTER(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(acquired_after(__VA_ARGS__))#define ABSL_ACQUIRED_BEFORE(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(acquired_before(__VA_ARGS__))// ABSL_EXCLUSIVE_LOCKS_REQUIRED() / ABSL_SHARED_LOCKS_REQUIRED()//// Documents a function that expects a mutex to be held prior to entry.// The mutex is expected to be held both on entry to, and exit from, the// function.//// An exclusive lock allows read-write access to the guarded data member(s), and// only one thread can acquire a lock exclusively at any one time. A shared lock// allows read-only access, and any number of threads can acquire a shared lock// concurrently.//// Generally, non-const methods should be annotated with// ABSL_EXCLUSIVE_LOCKS_REQUIRED, while const methods should be annotated with// ABSL_SHARED_LOCKS_REQUIRED.//// Example:////   Mutex mu1, mu2;//   int a ABSL_GUARDED_BY(mu1);//   int b ABSL_GUARDED_BY(mu2);////   void foo() ABSL_EXCLUSIVE_LOCKS_REQUIRED(mu1, mu2) { ... }//   void bar() const ABSL_SHARED_LOCKS_REQUIRED(mu1, mu2) { ... }#define ABSL_EXCLUSIVE_LOCKS_REQUIRED(...)   \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE( \      exclusive_locks_required(__VA_ARGS__))#define ABSL_SHARED_LOCKS_REQUIRED(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(shared_locks_required(__VA_ARGS__))// ABSL_LOCKS_EXCLUDED()//// Documents the locks acquired in the body of the function. These locks// cannot be held when calling this function (as Abseil's `Mutex` locks are// non-reentrant).#define ABSL_LOCKS_EXCLUDED(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(locks_excluded(__VA_ARGS__))// ABSL_LOCK_RETURNED()//// Documents a function that returns a mutex without acquiring it.  For example,// a public getter method that returns a pointer to a private mutex should// be annotated with ABSL_LOCK_RETURNED.#define ABSL_LOCK_RETURNED(x) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(lock_returned(x))// ABSL_LOCKABLE//// Documents if a class/type is a lockable type (such as the `Mutex` class).#define ABSL_LOCKABLE ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(lockable)// ABSL_SCOPED_LOCKABLE//// Documents if a class does RAII locking (such as the `MutexLock` class).// The constructor should use `LOCK_FUNCTION()` to specify the mutex that is// acquired, and the destructor should use `UNLOCK_FUNCTION()` with no// arguments; the analysis will assume that the destructor unlocks whatever the// constructor locked.#define ABSL_SCOPED_LOCKABLE \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(scoped_lockable)// ABSL_EXCLUSIVE_LOCK_FUNCTION()//// Documents functions that acquire a lock in the body of a function, and do// not release it.#define ABSL_EXCLUSIVE_LOCK_FUNCTION(...)    \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE( \      exclusive_lock_function(__VA_ARGS__))// ABSL_SHARED_LOCK_FUNCTION()//// Documents functions that acquire a shared (reader) lock in the body of a// function, and do not release it.#define ABSL_SHARED_LOCK_FUNCTION(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(shared_lock_function(__VA_ARGS__))// ABSL_UNLOCK_FUNCTION()//// Documents functions that expect a lock to be held on entry to the function,// and release it in the body of the function.#define ABSL_UNLOCK_FUNCTION(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(unlock_function(__VA_ARGS__))// ABSL_EXCLUSIVE_TRYLOCK_FUNCTION() / ABSL_SHARED_TRYLOCK_FUNCTION()//// Documents functions that try to acquire a lock, and return success or failure// (or a non-boolean value that can be interpreted as a boolean).// The first argument should be `true` for functions that return `true` on// success, or `false` for functions that return `false` on success. The second// argument specifies the mutex that is locked on success. If unspecified, this// mutex is assumed to be `this`.#define ABSL_EXCLUSIVE_TRYLOCK_FUNCTION(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE( \      exclusive_trylock_function(__VA_ARGS__))#define ABSL_SHARED_TRYLOCK_FUNCTION(...)    \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE( \      shared_trylock_function(__VA_ARGS__))// ABSL_ASSERT_EXCLUSIVE_LOCK() / ABSL_ASSERT_SHARED_LOCK()//// Documents functions that dynamically check to see if a lock is held, and fail// if it is not held.#define ABSL_ASSERT_EXCLUSIVE_LOCK(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(assert_exclusive_lock(__VA_ARGS__))#define ABSL_ASSERT_SHARED_LOCK(...) \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(assert_shared_lock(__VA_ARGS__))// ABSL_NO_THREAD_SAFETY_ANALYSIS//// Turns off thread safety checking within the body of a particular function.// This annotation is used to mark functions that are known to be correct, but// the locking behavior is more complicated than the analyzer can handle.#define ABSL_NO_THREAD_SAFETY_ANALYSIS \  ABSL_INTERNAL_THREAD_ANNOTATION_ATTRIBUTE(no_thread_safety_analysis)//------------------------------------------------------------------------------// Tool-Supplied Annotations//------------------------------------------------------------------------------// ABSL_TS_UNCHECKED should be placed around lock expressions that are not valid// C++ syntax, but which are present for documentation purposes.  These// annotations will be ignored by the analysis.#define ABSL_TS_UNCHECKED(x) ""// ABSL_TS_FIXME is used to mark lock expressions that are not valid C++ syntax.// It is used by automated tools to mark and disable invalid expressions.// The annotation should either be fixed, or changed to ABSL_TS_UNCHECKED.#define ABSL_TS_FIXME(x) ""// Like ABSL_NO_THREAD_SAFETY_ANALYSIS, this turns off checking within the body// of a particular function.  However, this attribute is used to mark functions// that are incorrect and need to be fixed.  It is used by automated tools to// avoid breaking the build when the analysis is updated.// Code owners are expected to eventually fix the routine.#define ABSL_NO_THREAD_SAFETY_ANALYSIS_FIXME ABSL_NO_THREAD_SAFETY_ANALYSIS// Similar to ABSL_NO_THREAD_SAFETY_ANALYSIS_FIXME, this macro marks a// ABSL_GUARDED_BY annotation that needs to be fixed, because it is producing// thread safety warning. It disables the ABSL_GUARDED_BY.#define ABSL_GUARDED_BY_FIXME(x)// Disables warnings for a single read operation.  This can be used to avoid// warnings when it is known that the read is not actually involved in a race,// but the compiler cannot confirm that.#define ABSL_TS_UNCHECKED_READ(x) absl::base_internal::ts_unchecked_read(x)namespace absl {inline namespace lts_2019_08_08 {namespace base_internal {// Takes a reference to a guarded data member, and returns an unguarded// reference.// Do not used this function directly, use ABSL_TS_UNCHECKED_READ instead.template <typename T>inline const T& ts_unchecked_read(const T& v) ABSL_NO_THREAD_SAFETY_ANALYSIS {  return v;}template <typename T>inline T& ts_unchecked_read(T& v) ABSL_NO_THREAD_SAFETY_ANALYSIS {  return v;}}  // namespace base_internal}  // inline namespace lts_2019_08_08}  // namespace absl#endif  // ABSL_BASE_THREAD_ANNOTATIONS_H_
 |