Ray Kraesig 1f4a9dd483 Bug 1207753 - add thread-safety annotations to memory/build's Mutex types r=glandium,jesup ... Add the customary bevy of thread-safety annotations to the Mutex types in memory/build. Almost all existing instances of these Mutexes are already marked with MOZ_UNANNOTATED, but this turns out not to matter: MOZ_UNANNOTATED has no equivalent under clang's `-Wthread-safety` attributes. There are no variables declared to be guarded by these mutexes, but they must still be unlocked and relocked in principled ways -- or, alternatively, only have unverifiable actions taken in appropriately-annotated code. The primary offenders here are the `pthread_atfork` hooks; these can't all be annotated precisely (and couldn't be checked even if they were), so we simply mark them all as unanalyzable. The only other warning is from a highly unusual (but already well-commented) bit in PHC.cpp where we manually release an autolocked mutex before crashing. Differential Revision: https://phabricator.services.mozilla.com/D150519		2022-07-08 21:24:03 +00:00
..
build	Bug 1207753 - add thread-safety annotations to memory/build's Mutex types r=glandium,jesup	2022-07-08 21:24:03 +00:00
gtest	Bug 1546442 - Add test for leading guard pages for normal allocations. r=glandium,pbone	2021-11-26 11:46:25 +00:00
mozalloc
mozjemalloc_info	Bug 1743713 - Make --enable-project=memory work again r=glandium	2021-12-07 22:27:20 +00:00
replace	Bug 1207753 - add thread-safety annotations to memory/build's Mutex types r=glandium,jesup	2022-07-08 21:24:03 +00:00
volatile	Bug 1207753 - Add MOZ_UNANNOTATED to all Mutexes/Monitors r=nika,kershaw	2022-03-16 18:47:08 +00:00
app.mozbuild
moz.build
moz.configure