Prefer packed representation for CompiledByteCode
As there are many 'CompiledByteCode' objects alive during a GHCi session, representing its element in a more packed manner improves space behaviour at a minimal cost. When running GHCi on the agda codebase, we find around 380 live 'CompiledByteCode' objects. Packing their respective 'UnlinkedByteCode' can save quite some pointers.
parent
12b997df
No related branches found
No related tags found
Pipeline #92797 canceled
Stage: tool-lint
Stage: quick-build
Stage: full-build
Stage: packaging
Stage: testing
Stage: deploy
Showing
- compiler/GHC/ByteCode/Asm.hs 4 additions, 3 deletionscompiler/GHC/ByteCode/Asm.hs
- compiler/GHC/ByteCode/Types.hs 2 additions, 2 deletionscompiler/GHC/ByteCode/Types.hs
- compiler/GHC/Data/FlatBag.hs 1 addition, 1 deletioncompiler/GHC/Data/FlatBag.hs
- compiler/GHC/Linker/Loader.hs 3 additions, 1 deletioncompiler/GHC/Linker/Loader.hs
- compiler/GHC/StgToByteCode.hs 3 additions, 2 deletionscompiler/GHC/StgToByteCode.hs
Loading