Update testsuite

[keithw]

The memory64 table.wast test has started to depend on function-references and gc (which WABT doesn't support yet), so vendor an older version of the test.

[sbc100]

The memory64 table.wast test has started to depend on function-references and gc (which WABT doesn't support yet), so vendor an older version of the test.

BTW, the reason for this is that memory64 is based on the wasm-3.0 branch of the spec repo where those proposals are already merged.

[sbc100]

Great! Thanks @keithw

lgtm % comments

[keithw]

The memory64 table.wast test has started to depend on function-references and gc (which WABT doesn't support yet), so vendor an older version of the test.

BTW, the reason for this is that memory64 is based on the wasm-3.0 branch of the spec repo where those proposals are already merged.

Makes sense -- I think this is going to become more painful for WABT over time as more proposals go this direction (at least until WABT implements function-references+gc or is refactored on top of wasm-tools or binaryen).

It's caused some issues in the https://github.com/WebAssembly/testsuite/ repo; e.g. memory64 doesn't change if.wast or br_if.wast or data.wast relative to wasm-3.0., but update-testsuite.sh still created https://github.com/WebAssembly/testsuite/blob/main/proposals/memory64/br_if.wast (etc.) because those files differ from the main branch. So it's a little more difficult for us to know what .txt files to create with this revision; test/update-spec-tests.py wants to make a lot of extra .txt files and we can't run most of them because they depend on wasm-3.0.

[sbc100]

The memory64 table.wast test has started to depend on function-references and gc (which WABT doesn't support yet), so vendor an older version of the test.

BTW, the reason for this is that memory64 is based on the wasm-3.0 branch of the spec repo where those proposals are already merged.

Makes sense -- I think this is going to become more painful for WABT over time as more proposals go this direction (at least until WABT implements function-references+gc or is refactored on top of wasm-tools or binaryen).

It's caused some issues in the https://github.com/WebAssembly/testsuite/ repo; e.g. memory64 doesn't change if.wast or br_if.wast or data.wast relative to wasm-3.0., but update-testsuite.sh still created https://github.com/WebAssembly/testsuite/blob/main/proposals/memory64/br_if.wast (etc.) because those files differ from the main branch. So it's a little more difficult for us to know what .txt files to create with this revision; test/update-spec-tests.py wants to make a lot of extra .txt files and we can't run most of them because they depend on wasm-3.0.

Ah yes, I guess we should modify update-testsuite.sh in the test suite repo so that it is aware that not all proposals forked from main.

[sbc100]

Can we remove test/regress/data-count-without-data-section.txt now that its coverted by the upstream test suite? @SoniEx2 ?

[SoniEx2]

sure!

[keithw]

sure!

Done.