<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Feb 24, 2013 at 3:40 PM, Gabor Greif <span dir="ltr"><<a href="mailto:ggreif@gmail.com" target="_blank">ggreif@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
from what I gathered so far no emission of write barriers is needed when<br>
- running on a uniprocessor (-threaded or not)<br>
- running on a multiprocessor sans having linked with -threaded.<br>
</blockquote></div><br></div><div class="gmail_extra">On Windows, the non-threaded RTS does I/O with forked threads; see rts/win32/IOManager.c and the async* functions in GHC.Conc.Windows. I think this means that for Windows, we need those write barriers even for non-threaded.<br>
<br></div><div class="gmail_extra">-Joey<br></div></div>