Also run all wasm tests explicitly with `--wasm-compiler=ion`
Categories
(Core :: JavaScript: WebAssembly, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox89 | --- | fixed |
People
(Reporter: jseward, Assigned: jseward)
References
Details
Attachments
(1 file)
Now that we have Ion support for wasm on all Tier-1 targets, it's important to
ensure that wasm tests are always run on Ion. That's won't necessarily happen
in the situation that wasm via Cranelift is also supported in the build,
because optimising wasm compilation might be routed via Cranelift instead.
Hence, to guarantee test coverage of Ion, we need to add
test-also=--wasm-compiler=ion
to all of the directives.txt
files in
jit-test/tests/wasm
.
Assignee | ||
Comment 1•3 years ago
|
||
Now that we have Ion support for wasm on all Tier-1 targets, it's important to
ensure that wasm tests are always run on Ion. That won't necessarily happen
in the situation that wasm via Cranelift is also supported in the build,
because optimising wasm compilation might be routed via Cranelift instead.
Hence, to guarantee test coverage of Ion, we need to add
test-also=--wasm-compiler=ion to all of the directives.txt files in
jit-test/tests/wasm.
Depends on D109860
Updated•3 years ago
|
Pushed by jseward@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8ec85768e9b1 Also run all wasm tests explicitly with `--wasm-compiler=ion`. r=lth.
Comment 3•3 years ago
|
||
bugherder |
Description
•