Don't export the _info symbol for the data constructor worker bindings
This is safe because GHC never generates a fast call to a data constructor worker: if the call is seen statically it will be eta-expanded and the allocation of the data will be inlined. We still need to export the _closure in case the constructor is used in an unapplied fashion.
Showing
- compiler/cmm/CLabel.hs 28 additions, 17 deletionscompiler/cmm/CLabel.hs
- compiler/cmm/CmmBuildInfoTables.hs 3 additions, 3 deletionscompiler/cmm/CmmBuildInfoTables.hs
- compiler/cmm/CmmDecl.hs 4 additions, 0 deletionscompiler/cmm/CmmDecl.hs
- compiler/cmm/CmmInfo.hs 3 additions, 3 deletionscompiler/cmm/CmmInfo.hs
- compiler/cmm/CmmParse.y 7 additions, 7 deletionscompiler/cmm/CmmParse.y
- compiler/cmm/OldPprCmm.hs 1 addition, 1 deletioncompiler/cmm/OldPprCmm.hs
- compiler/cmm/PprCmmDecl.hs 3 additions, 2 deletionscompiler/cmm/PprCmmDecl.hs
- compiler/codeGen/CgInfoTbls.hs 3 additions, 3 deletionscompiler/codeGen/CgInfoTbls.hs
- compiler/codeGen/ClosureInfo.lhs 16 additions, 6 deletionscompiler/codeGen/ClosureInfo.lhs
- compiler/codeGen/StgCmmClosure.hs 17 additions, 6 deletionscompiler/codeGen/StgCmmClosure.hs
- compiler/codeGen/StgCmmLayout.hs 1 addition, 1 deletioncompiler/codeGen/StgCmmLayout.hs
Loading
Please register or sign in to comment