SpecConstr: Introduce a separate argument limit for forced specs.
We used to put no limit at all on specializations forced via the SPEC argument. This isn't always reasonable so we introduce a very high limit that applies to forced specializations, a flag to control it, and we now emit a warning if we fail a specialization because we exceed the warning. Fixes #25197
parent
e4ac1b0d
No related branches found
No related tags found
Pipeline #101215 canceled
Stage: tool-lint
Stage: quick-build
Stage: full-build
Stage: packaging
Stage: testing
Stage: deploy
Showing
- compiler/GHC/Core/Opt/SpecConstr.hs 150 additions, 89 deletionscompiler/GHC/Core/Opt/SpecConstr.hs
- compiler/GHC/Driver/DynFlags.hs 3 additions, 0 deletionscompiler/GHC/Driver/DynFlags.hs
- compiler/GHC/Driver/Session.hs 2 additions, 0 deletionscompiler/GHC/Driver/Session.hs
- docs/users_guide/using-optimisation.rst 15 additions, 0 deletionsdocs/users_guide/using-optimisation.rst
- testsuite/tests/simplCore/should_compile/T25197.hs 30 additions, 0 deletionstestsuite/tests/simplCore/should_compile/T25197.hs
- testsuite/tests/simplCore/should_compile/T25197.stderr 6 additions, 0 deletionstestsuite/tests/simplCore/should_compile/T25197.stderr
- testsuite/tests/simplCore/should_compile/T25197_TH.hs 9 additions, 0 deletionstestsuite/tests/simplCore/should_compile/T25197_TH.hs
- testsuite/tests/simplCore/should_compile/all.T 1 addition, 0 deletionstestsuite/tests/simplCore/should_compile/all.T
Loading
-
mentioned in merge request !13184 (closed)
-
mentioned in commit 18860aa6
Please register or sign in to comment