Closed Bug 1471289 Opened 6 years ago Closed 6 years ago

Allow creation of WebAssembly.Global with type i64 if initial value is omitted in constructor call

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: lth, Assigned: lth)

Details

Attachments

(1 file)

Spec tweak from the CG meeting 2018-06-26: we should allow this to work (also for mutable globals):

  new WebAssembly.Global({value: 'i64'})

with the default value 0.  This just reduces annoyance.  We can already create such a global by creating it in wasm and exporting it.  For nonzero values we'll still have to do that.
Assignee: nobody → lhansen
Status: NEW → ASSIGNED
Attachment #8988422 - Flags: review?(jseward)
Comment on attachment 8988422 [details] [diff] [review]
bug1471289-default-i64-wasm-global.patch

Looks fine to me.
Attachment #8988422 - Flags: review?(jseward) → review+
Keywords: checkin-needed
Pushed by cbrindusan@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f2f1f75b9134
Handle 'new WebAssembly.Global' on i64 with default value. r=jseward
Keywords: checkin-needed
Pushed by lhansen@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7c3c2d6c17d7
Handle 'new WebAssembly.Global' on i64 with default value. r=jseward
https://hg.mozilla.org/mozilla-central/rev/7c3c2d6c17d7
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Flags: needinfo?(lhansen)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: