Re: [commit: ghc] master: Fix a couple of inaccurate stack checks (3bebf3c)

Hi Simon, with Am Mittwoch, den 05.11.2014, 18:15 +0000 schrieb git@git.haskell.org:
commit 3bebf3c2d92e6defc6d17ffa237cc4a9cad71dcf Author: Simon Marlow
Date: Tue Nov 4 21:31:00 2014 +0000 Fix a couple of inaccurate stack checks
I observe a 5% runtime performance regression in nofib’s "integer" benchmark: http://ghcspeed-nomeata.rhcloud.com/timeline/?exe=2&base=2%2B68&ben=nofib%2Ftime%2Finteger&env=2&revs=50&equid=on (The graph looks weird because codespeed doesn’t get the order of commits right.) Expected? Or worth looking into? Greetings, Joachim -- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org

Hi, Am Donnerstag, den 06.11.2014, 13:44 +0100 schrieb Joachim Breitner:
Am Mittwoch, den 05.11.2014, 18:15 +0000 schrieb git@git.haskell.org:
commit 3bebf3c2d92e6defc6d17ffa237cc4a9cad71dcf Author: Simon Marlow
Date: Tue Nov 4 21:31:00 2014 +0000 Fix a couple of inaccurate stack checks
I observe a 5% runtime performance regression in nofib’s "integer" benchmark: http://ghcspeed-nomeata.rhcloud.com/timeline/?exe=2&base=2%2B68&ben=nofib%2Ftime%2Finteger&env=2&revs=50&equid=on
(The graph looks weird because codespeed doesn’t get the order of commits right.)
Expected? Or worth looking into?
I’m no longer sure its caused by this commit. That test suddenly behaves rather erratic. Maybe it was something else that pushed it close to some GC run threshold. *shrug* Greetings, Joachim -- Joachim Breitner e-Mail: mail@joachim-breitner.de Homepage: http://www.joachim-breitner.de Jabber-ID: nomeata@joachim-breitner.de
participants (1)
-
Joachim Breitner