forks/wabt.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update testsuite (#2495)	Keith Winstein	2024-10-30	1	-15/+15
\| \| \| \| \|	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.
*	update br_table validation rule + enforce module validity in spectest-interp ↵	Keith Winstein	2022-04-13	1	-1/+1
\| \| \| \|	(#1895)
*	Fix function body start/end locations in wasm-validate (#1842)	Sam Clegg	2022-03-02	1	-2/+2
\| \| \| \| \| \| \| \| \| \|	For text validation, this means the error is always correctly reported on the final expression in the function. For binary validation, this means that we report the byte after the last instruction in the function as the failure location. This is in line with other binary validation reports. For example, for `type mismatch in i32.add` we report the validation error at the byte after the add instruction.
*	Remove check from binary-reader-interp.cc that the validator already ↵	Sam Clegg	2021-12-13	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	catches. NFC (#1784) If you leave stuff on the stack at the end of an initializer expression use the same mechanims to report the error as we do for functions etc. In addition, improve such errors so its more obvious what is going on.
*	Add error locations to BinaryReaderInterp (#1780)	Sam Clegg	2021-12-09	1	-7/+7
\| \| \| \|	I think it was always intended to work this way but was left as a TODO.
*	Update testsuite (#1738)	Sam Clegg	2021-10-18	1	-6/+12
\| \| \| \| \| \| \| \| \| \| \|	bulk-memory-operations and reference-types were completely removed from the upstream testsuite becuase there were merged into the upstream spec: https://github.com/WebAssembly/testsuite/pull/44 In order to land this I had to disable several spec tests under wasm2c because it lacks support for mutli-table and reference types. I filed #1737 to track this.
*	Mark memory_grow test as slow. (#1242)	Sam Clegg	2019-11-21	1	-0/+1
\| \| \| \| \|	On windows debug builds these seems to be taking a long time. Seems to have gotten worse since #1236 landed. I will continue to investigate the cause of the slowdown and possibly revert this.
*	interpreter: Allow traps to include custom error strings (#1236)	Sam Clegg	2019-11-19	1	-6/+6
\| \| \| \| \| \| \| \| \| \| \|	This means we can give more precise/useful errors for runtime failures. Change interp::Result from an enum to struct so it can hold the result enum plus an optional detailed error message. Add TRAP_MSG and TRAP_IF_MSG macros that work just like TRAP and TRAP_IF but contain a format string and printf-like arguments which are formatted to produce the error message.
*	spectest-interp: Report when assert_trap passes and include error string. ↵	Sam Clegg	2019-11-19	1	-0/+7
\| \| \| \|	NFC (#1235)
*	Update testsuite (#1047)	Ben Smith	2019-03-25	1	-1/+16
\|
*	Update to the lastest spec testsuite (#953)	Ben Smith	2018-11-07	1	-1/+1
\|
*	Update testsuite (#901)	Ben Smith	2018-08-24	1	-1/+1
\|
*	Update testsuite; enable mut. globals by default (#884)	Ben Smith	2018-08-03	1	-0/+5
	The newest testsuite update enables mutable globals by default, which matches the v1 WebAssembly spec. This change changes the default for all wabt tools, and changes the flag to `--disable-mutable-globals` in case you need the previous behavior. This flag will likely be removed in the future.