It's a little bit more complicated for me since some tests just plain
hang. I will investigate, though.
On Jul 11, 2006, at 2:56 AM, Donald Bruce Stewart wrote:
Not too bad (mips64 is around the same), but not the same as the
linux head:
[...]
So the next step would be to diff the two resul
On Tuesday 04 July 2006 13:20, Simon Peyton-Jones wrote:
> Lexically-scoped type variables are undergoing a slight upheaval in GHC 6.6
> that has not quite settled, and that is what you are running into.
Thanks for the help. After a lot of trial & error, and reading and stuff I've
got past the p
Joel Reymont wrote:
It's a little bit more complicated for me since some tests just plain
hang. I will investigate, though.
Which ones hang? Could you take one of the hanging tests, compile it with
-debug, run with +RTS -Ds, and send us the output?
Cheers,
Simon
___
On Jul 11, 2006, at 11:00 AM, Simon Marlow wrote:
Which ones hang? Could you take one of the hanging tests, compile
it with -debug, run with +RTS -Ds, and send us the output?
What ends up happening is this:
28683 p2 S 0:00.11 ../../timeout/timeout 300 cd ./typecheck/
should_compile &
I have a question about {-# RULES #-} pragmas. Here is a very simple
attempt to use them:
module Simplest where
{-# RULES
"simplestRule" forall x. id (id x) = x
#-}
myDefn = id (id 42)
I want to verify whether ghc-6.4.1 does actually fire this rule, but
have so far
Christian Maeder schrieb:
> It doesn't work under solaris and under linux [1] my nightly compilation
> jobs are "killed" every tuesday morning (!) for some reason that i
> cannot reproduce. I suspect the threaded RTS and heavy load. I had no
> such problems with ghc-6.4.1 before.
I withdraw my sus
Malcolm.Wallace:
> I have a question about {-# RULES #-} pragmas. Here is a very simple
> attempt to use them:
>
> module Simplest where
> {-# RULES
> "simplestRule" forall x. id (id x) = x
> #-}
> myDefn = id (id 42)
>
> I want to verify whether ghc-6.4.1 does actu
