Closed Bug 1796315 Opened 8 months ago Closed 7 months ago

Fixes to get Dart programs working


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




109 Branch
Tracking Status
firefox109 --- fixed


(Reporter: rhunt, Assigned: rhunt)


(Blocks 1 open bug)



(4 files)

No description provided.

This assert should be checking WordBits, not WordSize.

This commit:

  • Uses a consistent style of iterating backwards over struct fields
  • Changes array.new_fixed in baseline to init backwards, aligning with InitExpr and V8
  • Fixes WAO::fillVal when itemIndex != 0 (a latent bug, not triggerable)

Depends on D159793

This fixes it to use the one in V8's milestone 6. For sanity
sake we keep allowing the version used by wasm-tools, and will
remove it once we do our next update.

Depends on D159794

This commit remove WASM_PRIVATE_REFTYPES which is from the original prototype
that Lars wrote. It's not been needed since we added 'isExposable' to prevent
certain wasm values such as V128 from going to JS, and used that for GC

This commit also removes the restriction on non-nullable globals. The
globals JS-API supports non-nullable globals, and the internal
wasm type system should ensure all globals are initialized to

As a drive-by, the table.get() JS-API was updated to not work when the
table has a non-exposable value type.

Depends on D159795

The severity field is not set for this bug.
:rhunt, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(rhunt)
Severity: -- → N/A
Type: defect → task
Flags: needinfo?(rhunt)
Pushed by
wasm: Fix assert in UnsetLocalsState. r=yury
wasm: Standardize iteration of struct/array new instructions. r=jseward
wasm: Fix recursion group prefix byte. r=yury
wasm: Remove 'private reftypes' and allow non-nullable globals. r=yury
You need to log in before you can comment on or make changes to this bug.