Hi,
nothing overly exciting, but since I am running this ghcspeed thing, I
guess I should inform you about changes, just to get some practice doing
that :-)
Due to various build failures, the AMP landing patch was not measured in
isolation, so these numbers reflect the effect of these patches:
$
Hello Joachim,
You are probably seeing the effects of this bug for cryptarithm1:
https://ghc.haskell.org/trac/ghc/ticket/9570#ticket
Cheers,
Edward
Excerpts from Joachim Breitner's message of 2014-09-12 09:52:14 -0400:
> Hi,
>
> nothing overly exciting, but since I am running this ghcspeed
Hi,
Am Freitag, den 12.09.2014, 10:00 -0400 schrieb Edward Z. Yang:
> You are probably seeing the effects of this bug for cryptarithm1:
>
> https://ghc.haskell.org/trac/ghc/ticket/9570#ticket
possibly. But you report runtime differences without changes in
allocation numbers, whereas I obser
On Fri, Sep 12, 2014 at 3:52 PM, Joachim Breitner
wrote:
> nothing overly exciting, but since I am running this ghcspeed thing, I
> guess I should inform you about changes, just to get some practice doing
> that :-)
I'm very much in support of doing this.
Once we think pagespeed is stable enou
Hi,
Am Freitag, den 12.09.2014, 16:10 +0200 schrieb Johan Tibell:
> Once we think pagespeed is stable enough, I would be for sending
> automated emails on regressions.
it is quite noisy, which is mostly due to the fact that I track the
„number of failing testcases“ as a performance value, whic
