summaryrefslogtreecommitdiff
path: root/scripts/sha256sum.py
diff options
context:
space:
mode:
authorBen Smith <binji@chromium.org>2020-11-23 16:38:39 -0800
committerGitHub <noreply@github.com>2020-11-23 16:38:39 -0800
commitb5fdd589261813b2c3b2a49d6829a21f3b7f834a (patch)
treeeec474c2dc0db80cf0cb9752448155b575946eed /scripts/sha256sum.py
parent96001693fb1694318630675ea69e832412b624c4 (diff)
downloadwabt-b5fdd589261813b2c3b2a49d6829a21f3b7f834a.tar.gz
wabt-b5fdd589261813b2c3b2a49d6829a21f3b7f834a.tar.bz2
wabt-b5fdd589261813b2c3b2a49d6829a21f3b7f834a.zip
Fix func.wast spec test (#1574)
Fix spec test failure in func.wast The wasm text format allows the use of a function type to be specified one of three ways: ``` ;; 1. As an explicit type index or symbol (type 0) ;; 2. As params and results (param i32) (result i64) ;; 3. Both; an explicit type index, params and results (type 0) (param i32) (result i64) ``` Options 2 and 3 are text format sugar, since the binary format always encodes these as an explicit type index. Option 3 needs to check that the type at that index matches the explicitly given params and results. Normally checking whether an index is in bounds is a validation step, not a syntax checking step. However, in this case if the index is out of bounds, then the types cannot be checked, so it must be a syntax error.
Diffstat (limited to 'scripts/sha256sum.py')
0 files changed, 0 insertions, 0 deletions