tree 49e7fa59e7fa89421a4dfa50b522b1e1192dd884
parent 1b066cb3101dade3fe5be69218a7de41fa79599f
author Derek Schuff <dschuff@chromium.org> 1730417001 -0700
committer Derek Schuff <dschuff@chromium.org> 1730417001 -0700

Don't use multiple tables in wasm-split

Currently, wasm-split will create a second table rather than replacing
the existing one when reftypes is supported (or rather whether a
target_features section is present indicating it's already used).
But the emscripten integration code doesn't currently support this,
and it's not tested anywhere. The existing tests started failing when
Binaryen stopped stripping the features section by default.
(But some users would already be broken by this). For now, removing
this untested behavior is a safe default.