diff options
author | Thomas Lively <tlively@google.com> | 2024-04-24 11:07:28 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-04-24 11:07:28 -0700 |
commit | c183dc9ce6b6e14581078ba42ff1824f922234ca (patch) | |
tree | 75efc6dde4de579fa3e347d7e8b2cc31224cd3ca /test/spec/i64.load64_u.fail.wast | |
parent | ff02ea0bbe7e3288a2463bb449eb74a2753dda10 (diff) | |
download | binaryen-c183dc9ce6b6e14581078ba42ff1824f922234ca.tar.gz binaryen-c183dc9ce6b6e14581078ba42ff1824f922234ca.tar.bz2 binaryen-c183dc9ce6b6e14581078ba42ff1824f922234ca.zip |
[Parser] Use the new parser in wasm-shell and wasm-as (#6529)
Updating just one or the other of these tools would cause the tests
spec/import-after-*.fail.wast to fail, since only the updated tool would
correctly fail to parse its contents. To avoid this, update both tools at
once. (The tests erroneously pass before this change because check.py does not
ensure that .fail.wast tests fail, only that failing tests end in .fail.wast.)
In wasm-shell, to minimize the diff, only use the new parser to parse modules
and instructions. Continue using the legacy parsing based on s-expressions for
the other wast commands. Updating the parsing of the other commands to use
`Lexer` instead of `SExpressionParser` is left as future work. The boundary
between the two parsing styles is somewhat hacky, but it is worth it to enable
incremental development.
Update the tests to fix incorrect wast rejected by the new parser. Many of the
spec/old_* tests use non-standard forms from before Wasm MVP was standardized,
so fixing them would have been onerous. All of these tests have non-old_*
variants, so simply delete them.
Diffstat (limited to 'test/spec/i64.load64_u.fail.wast')
0 files changed, 0 insertions, 0 deletions