Hello Simon,
> $ ghc-nightly2 ./kazu.hs -O2 -fforce-recomp; time ./kazu
> [1 of 1] Compiling Main ( kazu.hs, kazu.o )
> Linking kazu ...
> 4.17s real 4.16s user 0.01s system 99% ./kazu
OK. I ran it on 32bit Linux.
6.12.3 runghc -- 2.22s user 0.40s system 96% cpu 2.724 total
> If I compile the attach code with GHC of the newest ghc-7.0 darcs
> branch, the compiled program is much slower than byte code. This
> phenomenon does not exist in GHC 6.12.3.
>
> 6.12.3 runghc -- 6.23s user 0.59s system 98% cpu 6.912 total
> ghc -- 5.72s user 0.70s system 99% c
> I'd expect the following program (compiled with ghc and without any
> specieal flags) to produce
>
>Just (Exited ExitSuccess)
>True
>
> but it produces
>
>Just (Exited ExitSuccess)
>False
>
> on Debian Lenny (ghc-6.8), OpenBSD-current (ghc-6.12.3), OpenBSD-current
> (ghc=7.0 from
Does the following code help you out? (Do note it's for the GHC 6.12.* API)
It just uses the the default GHC driver, meaning you don't have to separately
call the desugerar, simplifier, etc.
It's what I use for my CλaSH tool.
Cheers, Christiaan
-- External Modules
import qualified GHC.Paths
--
