On 01/09/2010 04:22, Edward Z. Yang wrote:
Not sure what you mean here: what's a bound FFI call?
Good point: we don’t distinguish between FFI calls that require thread
local state and which ones don’t: this might be a good thing to allow
annotating. If we did know, then we could simply arrang
It's a bit of a moveable feast. With -fno-spec-constr-count you allow GHC to
specialise as much as it pleases, which is good for perf (maybe) but can lead
to major code size expansion.
S
From: Johan Tibell [mailto:johan.tib...@gmail.com]
Sent: 31 August 2010 10:16
To: Simon Peyton-Jones
Cc: Br
I have some custom compilation script that uses GHC API
The aim is to extract some info from every module in dependency graph
and to write this information to the file lying near module-file.
Script goes like this:
main :: IO ()
main =
do args <- getArgs
defaultErrorHandler defaultDynFlags
Hi!
I am attaching a program which locks (throws an exception <>)
when compiled like:
ghc --make -threaded -main-is Test.main Test.hs -o test
and doesn't lock when compiled with
ghc --make -threaded -main-is -O2 Test.main Test.hs -o test
This should probably not happen.
I am using 6.12.3 on L
I cooked up a Darcs patch implementing the new language keyword 'interruptible'
sans tests, Windows support and avoiding executing interruptible calls on bound
worker threads. However, being a Darcs newbie I ended up sending the patch to
cvs-ghc, not this list. Let me know if you'd like me to exp
