Closed Bug 1416766 Opened 2 years ago Closed 2 years ago

wasm: fix i64 throwing behavior for globals / imported/exported functions

Categories

(Core :: JavaScript Engine: JIT, enhancement)

enhancement
Not set

Tracking

()

RESOLVED FIXED
mozilla59
Tracking Status
firefox58 --- wontfix
firefox59 --- fixed

People

(Reporter: bbouvier, Assigned: bbouvier)

References

Details

Attachments

(2 files)

No description provided.
Blocks: 1415224
Attached patch 1.globals.patchSplinter Review
Attachment #8927848 - Flags: review?(luke)
Comment on attachment 8927848 [details] [diff] [review]
1.globals.patch

Review of attachment 8927848 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks!
Attachment #8927848 - Flags: review?(luke) → review+
Comment on attachment 8927849 [details] [diff] [review]
2.functions.patch

Review of attachment 8927849 [details] [diff] [review]:
-----------------------------------------------------------------

Nice!
Attachment #8927849 - Flags: review?(luke) → review+
Pushed by bbouvier@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/91858a00db91
Int64 wasm globals should cause a link failure at instanciation time, not compile time; r=luke
https://hg.mozilla.org/integration/mozilla-inbound/rev/75c9879941ee
Immediately throw if an exported wasm function has int64 in the signature; r=luke
https://hg.mozilla.org/mozilla-central/rev/91858a00db91
https://hg.mozilla.org/mozilla-central/rev/75c9879941ee
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Won't fix for 58, let it ride the train.
You need to log in before you can comment on or make changes to this bug.