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)
commit080c9600d0ca63cc4125c6d2957ed8336b311c76
tree91ec2df6a4cab2a6cb6da2f2877cd1c21780eb06
parentcd0bb88bca4b8e082e67c455cc17da1b779bb477
takeMVar/putMVar were missing some write barriers when modifying a TSO

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.
ghc/rts/PrimOps.cmm
ghc/rts/Schedule.h