Some of the parallel benchmarks aren't very stable with a limited number
of iterations so don't run them by default. They used to be not run at
all! So not a huge change imo.

Also bump the base bounds to make newer ghcs work again.

This can be used via passing --head to the nofib runner.

It will build benchmark dependencies using the given benchmark compiler
and hackage.head.

Ben Gamari authored 4 years ago and Ben Gamari committed 4 years ago

The build system now does this automatically.

The rule did not produce this file.

We rather generate `Main.cachegrind.result.<n>`. For now I'll just let
this fact go unrepresented in the build graph.

To avoid interfering with test output.

This introduces a Shake-based build system, building on Neil Mitchell's
prototype from several years ago [1].

This build system has a number of features relative to the existing
make-based build system:

 * results are produced in a common CSV structure, making it easy to use
   the included analysis tool nofib-compare, to compare results from tests
   outside of nofib.
 * Cachegrind runs can be run in parallel, greatly speeding up such
   measurements
 * native support for (micro-)architectural performance counters on
   Linux via `perf stat`

[1] https://gist.github.com/ndmitchell/4733855

There are also a few more changes to tests to make this build system
work well with nofib.

In particular:

* The Main module for some benchmarks has been renamed.
* The boot phase of benchmarks is now done by a boot.sh script.
* Replace some uses of perl with ghci.
* Some benchmarks that we didn't use to run by default had
  missing/wrong(!) stdout files. I added/updated these.

Take note that shake will run *more* benchmarks by default than make
used to. So you might want to select a subset of benchmarks to run when
using it.