- 13 Dec, 2022 1 commit
-
-
Sebastian Graf authored
-
- 17 Sep, 2022 1 commit
-
-
Andreas Klebinger authored
-
- 22 Jun, 2022 2 commits
-
-
Andreas Klebinger authored
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.
-
Andreas Klebinger authored
-
- 11 Jun, 2022 2 commits
-
-
Benjamin Maurer authored
Increased input size and added argument for iteration count. Run-times were: 0.095s/0.651s/3.257s Are now: 0,145s/1,551s/8,064s
-
Benjamin Maurer authored
Times on Ryzen 4700 laptop (16GB): From 0.038s/0.310s/1.474s To 0.112s/1.222s/7.051s
-
- 06 Jun, 2022 2 commits
-
-
Benjamin Maurer authored
Input generation with the shake-based nofib-run didn't work for shootout/reverse-complement, so the test was never run. Created a boot.sh script analogous to shootout/k-nucleotide. Compilation of fasta-c.c and revcomp-c.c gave warnings for ignored return values of 'write' - suppressed them by explicitly ignoring with '(void)!' (negation and void cast).
-
Benjamin Maurer authored
real/smallpt's .slowstdout file was missing. The value in spectral/dom-lt's was wrong, also runtime was lower than 5 sek on my machine (should be between 5-10s), so I increased the argument and updated dom-lt.slowstdout.
-
- 05 Jun, 2022 1 commit
-
-
Benjamin Maurer authored
bc. program invocation on shake based nofib-run was broken. Also added a few arguments to input to make single iteration longer and adjusted iteration counts to get desired execution times.
-
- 04 Apr, 2022 3 commits
-
-
Andreas Klebinger authored
ghc-9 introduces a regression(?) in FP precision (See ghc ticket #19569). While this is unfortunate we want nofib to be useable with ghc 8.10 and 9.0 as far as possible. So I added an additional argument to the benchmark which controls if we output the benchmark result or not, which is off by default. This allows easy checking of the output manually without causing benchmark errors because the output differs. I've also added the benchmark to the ghc testsuite to avoid future regressions.
-
-
Andreas Klebinger authored
-
- 13 Mar, 2022 1 commit
-
-
Alex D authored
-
- 10 Mar, 2022 2 commits
-
-
Ben Gamari authored
-
Ben Gamari authored
-
- 06 Mar, 2022 1 commit
-
-
- 02 Mar, 2022 1 commit
-
-
Current test does some floating-point manipulations which can be non-deterministic due to different platforms/architectures. This change truncates the result to avoid potential stdout mismatch.
-
- 13 Nov, 2021 1 commit
-
-
By reducing the size of the raytraced image.
-
- 07 Nov, 2021 1 commit
-
-
- 18 Oct, 2021 2 commits
-
-
Matthew Pickering authored
-
Matthew Pickering authored
-
- 12 Oct, 2021 2 commits
-
-
Matthew Pickering authored
-
Matthew Pickering authored
-
- 16 Sep, 2021 1 commit
-
-
Ben Gamari authored
-
- 07 Sep, 2021 4 commits
-
-
Ben Gamari authored
-
Ben Gamari authored
-
Ben Gamari authored
-
Ben Gamari authored
-
- 06 Jul, 2021 2 commits
-
-
Andreas Klebinger authored
-
Matthew Pickering authored
-
- 29 May, 2021 1 commit
-
-
Oleg Grenrus authored
-
- 07 May, 2021 1 commit
-
-
- 06 May, 2021 8 commits
-
-
Andreas Klebinger authored
-
Andreas Klebinger authored
-
Andreas Klebinger authored
-
Andreas Klebinger authored
-
Andreas Klebinger authored
This can be used via passing --head to the nofib runner. It will build benchmark dependencies using the given benchmark compiler and hackage.head.
-
Andreas Klebinger authored
-
Andreas Klebinger authored
-
Andreas Klebinger authored
* We adjust for the specialisation of Data.List by hiding the generic version from the Prelude. This should make this change backwards compatible with older base versions. * Adjust the gc benchmarks. I've mostly made them the same as their non-gc parts now.
-