See [this discussion](%) for background info. It's not obvious to me how to handle lazy bytecode in these cases – using it naively may increase memory usage significantly. These sites obtain lazy bytecode from the `HomeModInfo` interface. Outside of the compilation pipeline, its consumers are: * `upsweep_mod` * to provide the old `Linkable` from the GHCi cache to `compileOne'` * for `addSptEntries` after compilation * `getModBreaks` * `getLeakIndicators` It would be useful to create a dedicated and more explicit interface for these cases that require use sites to declare whether they want to force lazy bytecode.