On 09/02/2011 09:25, Kazu Yamamoto (山本和彦) wrote:
Hello,
My stats look very different.
6 RuleFired
1 ++
2<=#
1 foldr/app
1 unpack
1 unpack-list
Are your libraries compiled with -O2?
I don't know. How can I check?
I just installed ghc-7.0 by "perl boot; configure; ma
Hello,
> My stats look very different.
>
> 6 RuleFired
> 1 ++
> 2 <=#
> 1 foldr/app
> 1 unpack
> 1 unpack-list
>
> Are your libraries compiled with -O2?
I don't know. How can I check?
I just installed ghc-7.0 by "perl boot; configure; make; make install".
--Kazu
_
On 09/02/2011 04:35, Kazu Yamamoto (山本和彦) wrote:
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 --
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
Hello,
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% cpu 6
