|author||Rich Felker <email@example.com>||2020-05-22 17:45:47 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2020-05-22 17:45:47 -0400|
the design used here relies on the barrier provided by the first lock operation after the process returns to single-threaded state to synchronize with actions by the last thread that exited. by storing the intent to change modes in the same object used to detect whether locking is needed, it's possible to avoid an extra (possibly costly) memory load after the lock is taken.
Diffstat (limited to 'crt')
0 files changed, 0 insertions, 0 deletions