diff options
| author | Sam Clegg <sbc@chromium.org> | 2021-10-13 09:16:02 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-13 09:16:02 -0700 |
| commit | e1b6676d09c315dc974670a0b364143f39d3a7d7 (patch) | |
| tree | a67cc8434f9aaa8743fa0a59db709f49cea26090 /scripts | |
| parent | f64f393ff0bad3a33e97084ce63dcf18b13f335c (diff) | |
| download | wabt-e1b6676d09c315dc974670a0b364143f39d3a7d7.tar.gz wabt-e1b6676d09c315dc974670a0b364143f39d3a7d7.tar.bz2 wabt-e1b6676d09c315dc974670a0b364143f39d3a7d7.zip | |
Avoid writing DataCount section when it is not needed. (#1727)
Without this change, when bulk memory is enabled, the DataCount is
always written when then removed if it proves that its not needed by any
instruction.
However, if we know there are no data segments we can avoid writing it
altogether. This happens to be more compact but I'm hoping to land this
now in anticipation of enabled bulk memory by default. Once we do that
we don't want all the `dump` tests to include the writing and truncating
of the DataCount section in cases when there is no data.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions