No description

Gareth Rees d56741e1ea In order to be able to test mps_arena_busy in all build configurations, we must always take and release the arena lock, even in the single-threaded case. we gain some additional checking by doing this, at low cost (since in this build configuration the locks are generic and so just increment/decrement a count of claims). ... In the CONFIG_POLL_NONE we configuration, we would still like to check that no traces are busy when leaving the arena, but since we now call ArenaLeave in this configurations, move the assertion to ShieldLeave. In ArenaDestroy, call ArenaLeave, don't just release the lock. Copied from Perforce Change: 192267 ServerID: perforce.ravenbrook.com		2016-09-09 13:01:25 +01:00
mps	In order to be able to test mps_arena_busy in all build configurations, we must always take and release the arena lock, even in the single-threaded case. we gain some additional checking by doing this, at low cost (since in this build configuration the locks are generic and so just increment/decrement a count of claims).	2016-09-09 13:01:25 +01:00