Building GHC for performance testing

Carter Schonwald carter.schonwald at gmail.com
Sat Mar 8 17:46:19 UTC 2014


one idea that I think Ben Gamari (or was it Reid?) pointed out is that
another (potentially valuable) metric is "how long does it take for ghc to
build itself"


On Sat, Mar 8, 2014 at 5:20 AM, Simon Marlow <marlowsd at gmail.com> wrote:

> On 08/03/14 07:54, Herbert Valerio Riedel wrote:
>
>> Hi Simon,
>>
>> On 2014-03-08 at 08:18:20 +0100, Simon Marlow wrote:
>>
>>> On 06/03/14 09:50, Johan Tibell wrote:
>>>
>>
>> [...]
>>
>>     * Are there any tweaks to mk/build.mk <http://build.mk> we can do to
>>>> make the build faster without compromising the results?
>>>>
>>>
>>> Turn down the stage2 optimisation, and turn off the docs:
>>>
>>> GhcStage2HcOpts = -O
>>>
>>
>> ...but doesn't that compromise the compile-time metrics collected by
>> nofib about GHC's performance?
>>
>
> I think Johan is interested primarily in runtime performance, but yes if
> you care about compile time then it's better to leave GhcStage2HcOpts at
> the default.
>
> Cheers,
> Simon
>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20140308/14952c04/attachment.html>


More information about the ghc-devs mailing list