Closed Bug 1733655 Opened 3 years ago Closed 3 years ago

Enable non-MVP features with wasm-smith fuzzing

Categories

(Core :: JavaScript: WebAssembly, task, P3)

task

Tracking

()

RESOLVED FIXED
95 Branch
Tracking Status
firefox95 --- fixed

People

(Reporter: rhunt, Assigned: rhunt)

Details

Attachments

(2 files, 1 obsolete file)

wasm-smith has a config option that allows enabling non-MVP features. We should enable these. We should also update our wasm-smith for exception-handling support.

Update the vendored copy of wasm-smith to 0.8.0.

Depends on D127297

Add and use a manual config implementation that enables proposals
that we have any amount of support for. This commit does not enable
any features on the runtime side that aren't enabled by default.

Depends on D127298

There is one patch attached that fixes a non-security issue I found while running fuzzing with these patches. Upon further review of the code, I believe the patch may be unnecessary and only fixes an issue due to how my local patch enabled exception-handling support in the fuzzer. I need to do some more investigation on it.

Priority: -- → P3
Pushed by rhunt@eqrion.net:
https://hg.mozilla.org/integration/autoland/rev/393b1a897117
wasm: Update wasm-smith for exception-handling support. r=decoder
https://hg.mozilla.org/integration/autoland/rev/519f76cce21a
wasm: Enable non-MVP features that we have support for in wasm-smith. r=decoder
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
Attachment #9243979 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: