When I compile the follow code
main :: IO()
main = print ((iterate anyFunc 3)!!8)
is generated, in the core representation, a call to iterateFB1 instead of
iterate. Does this happen due to rule described below?
{-# RULES
"iterate"[~1] forall f x.iterate f x = build (\c _n -> iterateFB c
On 3/7/08, Guilherme Avelino <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I´m using the flag -fext-core to obtain the core of a program. But, rewrite
> rules not changed this code. Are there any way to observe the changes cause
> by rewrite rules on Core language?
>
> For sample:
>
> iterate :: (a -> a) -
gavelino:
>Hi,
>
>I'm using the flag -fext-core to obtain the core of a program. But,
>rewrite rules not changed this code. Are there any way to observe the
>changes cause by rewrite rules on Core language?
>
Yeah, -ddump-simpl-iterations -ddump-simpl-stats
will show each iterat
Hi,
I´m using the flag -fext-core to obtain the core of a program. But, rewrite
rules not changed this code. Are there any way to observe the changes cause
by rewrite rules on Core language?
For sample:
iterate :: (a -> a) -> a -> [a]
iterate f x = x : iterate f (f x)
iterateFB c f x = x `c` i
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Fri Mar 7 18:00:01 GMT 2008.
checking out
Build description = STABLE on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Fri Mar 7 18:10:01 GMT 2008.
checkin
Thu Mar 6 05:50:26 PST 2008 [EMAIL PROTECTED]
* Don't expose the unfolding of dictionary selectors without -O
When compiling without -O we were getting code like this
f x = case GHC.Base.$f20 of
:DEq eq neq -> eq x x
But because of the -O the $f20 dictiona
Thu Mar 6 05:47:34 PST 2008 [EMAIL PROTECTED]
* Fix Trac #783: improve short-cutting literals in the type checker
The Inst.shortCutIntLit mechanism in the type checker was missing cases
where a floating-point literal was given without an explicit decimal point.
As a result, programs
Thu Mar 6 05:46:51 PST 2008 [EMAIL PROTECTED]
* Fix Trac #2138: print the 'stupid theta' of a data type
M ./compiler/main/PprTyThing.hs -2 +6
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Build results:
x86-64 Linux head:fail (failed darcs)
x86 Windows head: fail (failed bindisttest) fail (failed darcs)
x86 Windows head fast:pass pass fail (failed darcs) fail (failed darcs)
pass
kahl G5 Gentoo Linux head:pass
mnemosyne x86-64 Gentoo head: pass
tn
Build results:
kahl G5 Gentoo Linux stable: pass
x86 Windows stable: fail (failed bindisttest) fail (failed getsubrepos)
x86 Windows stable fast: pass pass fail (failed darcs) fail (failed darcs)
pass
x86-64 Linux stable: fail (failed darcs)
Fixed unexpected test failures:
11 matches
Mail list logo