haskell / haskell/cabal

Fix, benchmark and re-evaluate -fexpose-all-unfoldings and -fspecialise-aggressively

Open
#7,731 1 comment 1 reaction 0 assignees View on GitHub
priority: low recompilation type: performance
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

These had to be removed, because they caused OOM on armv7.

They bit-rotted (the Cabal optimization flags were probably not moved to the solver package when it was separated out), so the benchmarks in https://github.com/haskell/cabal/pull/7729#issuecomment-939052965 show they have negligible effect.

The `-fexpose-all-unfoldings` for `parsec` is a somewhat different story, but it needs re-evaluation as well, ideally sooner rather than later (low cost of slower compilation vs potentially higher gain). These benchmarks are probably still valid: https://github.com/haskell/cabal/commit/dcb23dd33fb3a76b4ab98b3f2100f851bb1d447e

I think, before 3.8 or after GHC 9.2 is out, whichever comes first, it makes sense to fix the optimizations and re-benchmark and then decide.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.