diff options
| author | Jacques Pienaar <jpienaar@google.com> | 2021-02-10 12:44:18 -0800 |
|---|---|---|
| committer | Jacques Pienaar <jpienaar@google.com> | 2021-02-10 12:44:18 -0800 |
| commit | 5e77ea04f214c7a18bd5c782c8b8a7b7c828ad7a (patch) | |
| tree | 7ec5bae21d3b8871fb62c88a931aa84e4000510c /clang/lib/Frontend/TestModuleFileExtension.cpp | |
| parent | 1cb47a063e2bbb04375ab52ed7377e8d555ef97d (diff) | |
| download | llvm-5e77ea04f214c7a18bd5c782c8b8a7b7c828ad7a.zip llvm-5e77ea04f214c7a18bd5c782c8b8a7b7c828ad7a.tar.gz llvm-5e77ea04f214c7a18bd5c782c8b8a7b7c828ad7a.tar.bz2 | |
Make gCrashRecoveryEnabled thread local
If context is enabled/disabled and queried concurrently then this
results in a data race/TSAN failure with RunSafely (where boolean
variable was not locked).
There doesn't seem to be a reasonable way to enable threads that enable
and disable recovery in parallel (without also keeping
gCrashRecoveryEnabled's lock held during Fn execution which seems
undesirable). This makes enable checking if enabled thread local and
consistent with other thread local usage of crash context here.
Differential Revision: https://reviews.llvm.org/D93907
Diffstat (limited to 'clang/lib/Frontend/TestModuleFileExtension.cpp')
0 files changed, 0 insertions, 0 deletions