You could tweak the function `checkStats` in `testsuite/driver/testlib.py` a bit, to not only report failures.

Maybe also disable the following check, if you're doing this from a debug build:

# Compiler performance numbers change when debugging is on, making the results

# useless and confusing. Therefore, skip if debugging is on.

if compiler_debugged():

skip(name, opts)

On Fri, Feb 12, 2016 at 9:30 PM, Richard Eisenberg <eir@cis.upenn.edu> wrote:

On Feb 12, 2016, at 3:28 PM, Simon Peyton Jones <simonpj@microsoft.com> wrote:

> cd testsuite/tests/perf; make

But that tells me only about failures. What if I have a tweak that makes an average 1% improvement over lots of files? That would be a nice improvement, but we don't have an easy way to collect this info, I think, other than perf.haskell.org.

_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs