>
> OTOH, certainly doing an IO operation should cause a thread switch.
> In my limited use of the concurrency extension, I found it hard to
> write a dining philosophers program that behaved randomly. I had to
> throw yield's in all over the place. The `GHC-specific concurrency
> issues' of t
I'm trying to build the latest version of GHC, from CVS, and everything goes
fine until it gets to the file Parser.hs. At this point, it gets stuck on this
file for a couple of hours, then quits with either an "out of memory" message
or the message "Haskell compiler received signal 9". I've tried
