Place static closures in their own section.
Summary: The primary reason for doing this is assisting debuggability: if static closures are all in the same section, they are guaranteed to be adjacent to one another. This will help later when we add some code that takes section start/end and uses this to sanity-check the sections. Part of remove HEAP_ALLOCED patch set (#8199) Signed-off-by:Edward Z. Yang <ezyang@mit.edu> Test Plan: validate Reviewers: simonmar, austin Subscribers: simonmar, ezyang, carter, thomie Differential Revision: https://phabricator.haskell.org/D263 GHC Trac Issues: #8199
Showing
- compiler/cmm/Cmm.hs 1 addition, 0 deletionscompiler/cmm/Cmm.hs
- compiler/cmm/CmmParse.y 1 addition, 1 deletioncompiler/cmm/CmmParse.y
- compiler/cmm/PprCmmDecl.hs 1 addition, 0 deletionscompiler/cmm/PprCmmDecl.hs
- compiler/codeGen/StgCmmBind.hs 2 additions, 2 deletionscompiler/codeGen/StgCmmBind.hs
- compiler/codeGen/StgCmmCon.hs 1 addition, 1 deletioncompiler/codeGen/StgCmmCon.hs
- compiler/codeGen/StgCmmUtils.hs 6 additions, 0 deletionscompiler/codeGen/StgCmmUtils.hs
- compiler/llvmGen/LlvmCodeGen/Data.hs 1 addition, 0 deletionscompiler/llvmGen/LlvmCodeGen/Data.hs
- compiler/nativeGen/PPC/Ppr.hs 1 addition, 0 deletionscompiler/nativeGen/PPC/Ppr.hs
- compiler/nativeGen/SPARC/Ppr.hs 1 addition, 0 deletionscompiler/nativeGen/SPARC/Ppr.hs
- compiler/nativeGen/X86/Ppr.hs 4 additions, 0 deletionscompiler/nativeGen/X86/Ppr.hs
Loading
Please register or sign in to comment