When memory is declared in the Wasm module, we rely on the implicit zero
initialization behavior and do not explicitly output .bss sections. The means
that they do not have associated outputSec entries, which was causing
segfaults in the mapfile support. Fix the issue by guarding against null
outputSec and falling back to using a zero offset.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
@sbc100 Is there anything better to do here besides falling back and emitting 0 as the offset?
Comment Actions
It does seem a little unfortunate that we can't report that offset correctly here. I would expect to see my bss always following by non-bss data. Let me take a look at see if we are relying on the null outputSec ...