We made a hack that disables GCs while wasm is running, but this lead to a flurry of fuzz bugs because many places in the engine check that GC can happen (either explicitly through `!suppressedGC` or implicitly after a check that an incremental GC has actually happened, for instance). At some point we should implement proper GC support. At this point, we need stack maps at the following locations: - before a call (direct or indirect, internal or external; except for leaf functions) - before an interrupt check (which could trigger an urgent GC) - before a memory allocation (when we implement gc.new in wasm) - (other places I can't think of right now)
Summary: wasm: Implement actual GC support in wasm → [meta] Implement proper GC support for wasm
All those hacks were just removed.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.