[project @ 2005-11-24 14:21:33 by simonmar]
unlockClosure() requires a write barrier for the compiler - write barriers aren't required for the CPU, but gcc re-orders non-aliasing writes unless we use an explicit barrier. This only just showed up when we started compiling the RTS with -O2.
Please register or sign in to comment