gecko-dev/memory
Emilio Cobos Álvarez a3e8abd326 Bug 1858250 - malloc_initialized should not be SequentiallyConsistent. r=glandium
I think ReleaseAcquire semantics are sound here.

It might be that relaxed is fine too, but that might be technically
unsound because it could make the writes in malloc_init_hard not visible
to the other threads in time.

Depends on D190623

Differential Revision: https://phabricator.services.mozilla.com/D190624
2023-10-11 08:09:03 +00:00
..
build Bug 1858250 - malloc_initialized should not be SequentiallyConsistent. r=glandium 2023-10-11 08:09:03 +00:00
gtest Bug 1798711 - Remove duplication of DisableCrashReporter on gtest r=ahal 2022-11-30 14:41:42 +00:00
mozalloc Bug 1854519 - Work around wasm linking issue before clang 11. r=firefox-build-system-reviewers,sergesanspaille 2023-09-28 20:56:31 +00:00
mozjemalloc_info Bug 1825329 - Make memory/moz*alloc buildable outside of a unified build environment r=andi 2023-03-31 13:29:45 +00:00
replace Bug 1814798 - pt 2. Add a PHCManager component to control PHC r=glandium,emilio 2023-09-18 06:48:06 +00:00
volatile Bug 1844908 - Remove pre-Win10-specific codepath from memory/. r=glandium 2023-07-26 08:52:51 +00:00
app.mozbuild
moz.build
moz.configure