WebAssembly / WebAssembly/wabt
wasm2c/spec/simd_address.txt fails on non-x86
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.1k
- Forks
- 827
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 18
Description
When running the test suite of wabt-1.0.33 on aarch64 on Fedora 38, I get this (new) test failure:
- test/wasm2c/spec/simd_address.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,11 @@
+Traceback (most recent call last):
+ File "/builddir/build/BUILD/wabt-1.0.33/test/run-spec-wasm2c.py", line 648, in <module>
+ sys.exit(main(sys.argv[1:]))
+ ^^^^^^^^^^^^^^^^^^
+ File "/builddir/build/BUILD/wabt-1.0.33/test/run-spec-wasm2c.py", line 642, in main
+ utils.Executable(main_exe, forward_stdout=True).RunWithArgs()
+ File "/builddir/build/BUILD/wabt-1.0.33/test/utils.py", line 95, in RunWithArgs
+ raise error
+utils.Error: Error running "out/test/wasm2c/spec/simd_address/simd_address" (1):
+None
+out/test/wasm2c/spec/simd_address/simd_address-main.c:499: assertion failed: expected w2c_simd__address__1__wasm_v1280x2Eload_offset_65521(&simd__address__1__wasm_instance) to trap.
STDOUT MISMATCH:
--- expected
+++ actual
@@ -1 +1 @@
-42/42 tests passed.
+41/42 tests passed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure on aarch64 Fedora 38 using test/wasm2c/spec/simd_address.txt and the wasm2c test suite. Start with test/run-spec-wasm2c.py and the generated simd_address-main.c path shown in the failure, then compare the non-x86 behavior with the expected trap. Done means the test reports 42/42 passed without stdout or stderr mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, wasm
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100