takeMVar/putMVar were missing some write barriers when modifying a TSO
authorSimon Marlow <simonmar@microsoft.com>
Tue, 28 Feb 2006 16:37:24 +0000 (16:37 +0000)
committerSimon Marlow <simonmar@microsoft.com>
Tue, 28 Feb 2006 16:37:24 +0000 (16:37 +0000)
This relates to the recent introduction of clean/dirty TSOs, and the
consqeuent write barriers required.  We were missing some write
barriers in the takeMVar/putMVar family of primops, when performing
the take/put directly on another TSO.

Fixes #705, and probably some test failures.


No differences found