summaryrefslogtreecommitdiff
path: root/utils
diff options
context:
space:
mode:
authorAndreas Klebinger <klebinger.andreas@gmx.at>2021-02-21 16:04:20 +0100
committerMarge Bot <ben+marge-bot@smart-cactus.org>2021-02-26 16:27:26 -0500
commita9f23793126251844944e00bca8e84370c759aa7 (patch)
tree29122c4a7ce6aafcc41d3b070f70697289e2db97 /utils
parent24777bb334a49f6bd6c0df2d5ddb371f98436888 (diff)
downloadhaskell-a9f23793126251844944e00bca8e84370c759aa7.tar.gz
Move absentError into ghc-prim.
When using -fdicts-strict we generate references to absentError while compiling ghc-prim. However we always load ghc-prim before base so this caused linker errors. We simply solve this by moving absentError into ghc-prim. This does mean it's now a panic instead of an exception which can no longer be caught. But given that it should only be thrown if there is a compiler error that seems acceptable, and in fact we already do this for absentSumFieldError which has similar constraints.
Diffstat (limited to 'utils')
-rw-r--r--utils/genprimopcode/Main.hs2
1 files changed, 1 insertions, 1 deletions
diff --git a/utils/genprimopcode/Main.hs b/utils/genprimopcode/Main.hs
index e6e89735e5..7fe672387c 100644
--- a/utils/genprimopcode/Main.hs
+++ b/utils/genprimopcode/Main.hs
@@ -622,7 +622,7 @@ gen_wrappers (Info _ entries)
-- Performing WW on this module is harmful even, two reasons:
-- 1. Inferred strictness signatures are all bottom, which is a lie
-- 2. Doing the worker/wrapper split based on that information will
- -- introduce references to Control.Exception.Base.absentError,
+ -- introduce references to absentError,
-- which isn't available at this point.
++ "module GHC.PrimopWrappers where\n"
++ "import qualified GHC.Prim\n"