Lines Matching refs:safety

16 Thread safety analysis works very much like a type system for multi-threaded
69 analysis issues a warning.  Thread safety analysis is not inter-procedural, so
85 To run the analysis, simply compile with the ``-Wthread-safety`` flag, e.g.
89   clang -c -Wthread-safety example.cpp
99 Thread safety analysis provides a way of protecting *resources* with
141 The thread safety analysis uses attributes to declare threading constraints.
147 For historical reasons, prior versions of thread safety used macro names that
314 turns off thread safety checking for that method.  It provides an escape hatch
438 * ``-Wthread-safety``:  Umbrella flag which turns on the following three:
440   + ``-Wthread-safety-attributes``: Sanity checks on attribute syntax.
441   + ``-Wthread-safety-analysis``: The core analysis.
442   + ``-Wthread-safety-precise``: Requires that mutex expressions match precisely.
444   + ``-Wthread-safety-reference``: Checks when guarded members are passed by reference.
449 * ``-Wthread-safety-negative``:  Negative capabilities.  Off by default.
455 * ``-Wthread-safety-beta``:  New features.  Off by default.
470 safety guarantee as REQUIRES.  In particular:
505 a stronger safety guarantee.  A negative requirement uses the  REQUIRES
540 by passing ``-Wthread-safety-negative``.
569 Thread safety attributes contain ordinary C++ expressions, and thus follow
597 Thread safety attributes follow normal C++ access restrictions, so if ``mu``
612     // For thread safety analysis only.  Does not actually return mu.
630 safety analysis.
672 Thread safety analysis is strictly intra-procedural, just like ordinary type
698 thread safety analysis cannot see the unlock, because it does not attempt to
746 Thread safety analysis can be used with any threading library, but it does
759   // Enable thread safety attributes only with clang.
883   // The original version of thread safety analysis the following attribute
885   // by existing thread safety code, and will continue to be supported.