Hello Seth,
Wednesday, June 21, 2006, 7:18:48 AM, you wrote:
Seth and Li, look at
http://www.cse.unsw.edu.au/~chak/haskell/ghc/comm/rts-libs/multi-thread.html
it may answer some of your questions
(page http://www.cse.unsw.edu.au/~chak/haskell/ghc/comm/ contains
commentaries about GHC internal
Another related question. I have some threaded applications running which are
servers and run continuously. A thread is spawned for each new connection, and
the thread exits when the client terminates.
I've noticed that the thread ID increases. On one process I checked today I am
up to threa
I have a related question. The docs state that in some environments O/S
threads are used when the -threaded flag is used with ghc, and non-O/S threads
are used otherwise (presumably these are non-preemptive). Does this apply as
well to the worker threads that are the subject of this email?
On
Hello,
The paper "Extending the Haskell FFI with Concurrency" mentioned the
following in Section 6.3:
"GHC's run-time system employs one OS thread for every bound thread;
additionally, there is a variable number of so-called "worker" OS
threads that are used to execute the unbounded (lightweight
Simon,
Yes, it's quite deliberate. See 5.4 of
http://research.microsoft.com/%7Esimonpj/papers/gadt/gadt-icfp.pdf
The alternative design choice is to reject both programs, but in
Haskell
(because of laziness) the evaluation order is prescribed, so accepting
the former seems right.
Yes, it's quite deliberate. See 5.4 of
http://research.microsoft.com/%7Esimonpj/papers/gadt/gadt-icfp.pdf
The alternative design choice is to reject both programs, but in Haskell
(because of laziness) the evaluation order is prescribed, so accepting
the former seems right.
Simon
| -
Hi all,
I have to admit that I haven't checked if this is a known issue...
The following is tested with both GHC 6.4.1 and 6.4.2; I have not
checked the HEAD.
Let me define a simple GADT |F|,
-- a simple GADT
data F :: * -> * where F :: Int -> F ()
and a more or less trivial function
