summaryrefslogtreecommitdiff
path: root/ghc/utils
diff options
context:
space:
mode:
authorSimon Marlow <simonmar@microsoft.com>2006-03-14 11:25:50 +0000
committerSimon Marlow <simonmar@microsoft.com>2006-03-14 11:25:50 +0000
commit960a5e6a6f604aa01f5f74b80fb0f61ceffd7ed3 (patch)
tree833e1b1db46d1998c612cabe5fd88fe5846bf346 /ghc/utils
parenta9dc96582699e24c7d67eec9e4296b80dee53e92 (diff)
downloadhaskell-960a5e6a6f604aa01f5f74b80fb0f61ceffd7ed3.tar.gz
Make it a fatal error to try to enter a PAP
This is just an assertion, in effect: we should never enter a PAP, but for convenience we previously attached the PAP apply code to the PAP info table. The problem with this was that it makes it harder to track down bugs that result in entering a PAP...
Diffstat (limited to 'ghc/utils')
-rw-r--r--ghc/utils/genapply/GenApply.hs2
1 files changed, 1 insertions, 1 deletions
diff --git a/ghc/utils/genapply/GenApply.hs b/ghc/utils/genapply/GenApply.hs
index a91226632c..cdde66fa78 100644
--- a/ghc/utils/genapply/GenApply.hs
+++ b/ghc/utils/genapply/GenApply.hs
@@ -457,7 +457,7 @@ genApply regstatus args =
nest 4 (vcat [
text "arity = TO_W_(StgPAP_arity(R1));",
text "ASSERT(arity > 0);",
- genMkPAP regstatus "NEW_PAP" "ENTRY_LBL(stg_PAP)" "PAP" "PAP"
+ genMkPAP regstatus "NEW_PAP" "stg_PAP_apply" "PAP" "PAP"
True{-stack apply-} False{-args on stack-} True{-is a PAP-}
args all_args_size fun_info_label
]),