Closed
Bug 1389458
Opened 7 years ago
Closed 4 years ago
[meta] Implement WebAssembly threads proposal
Categories
(Core :: JavaScript: WebAssembly, enhancement, P3)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
People
(Reporter: lth, Unassigned)
References
(Depends on 2 open bugs)
Details
(Keywords: dev-doc-complete, meta)
Attachments
(1 file, 4 obsolete files)
|
66.81 KB,
application/octet-stream
|
Details |
Proposal repo: https://github.com/WebAssembly/threads Main proposal text: https://github.com/WebAssembly/threads/blob/master/proposals/threads/Overview.md The proposal is stable and basically finished but may not be completely nailed down until the November 2017 CG meeting. If we land before then (and I think we should do that) we should land behind a NIGHTLY flag or similar.
|
Reporter | |
Updated•7 years ago
|
Priority: -- → P2
|
|
Reporter | |
Comment 1•7 years ago
|
||
WIP, mostly for safekeeping purposes. Atomics work (so far as a casual observer is concerned) in the baseline compiler; Ion is still missing 64-bit atomics. Most of the pieces are here but the Memory object does not allocate shared memory yet. Lots of work remains.
|
|
Reporter | |
Comment 2•7 years ago
|
||
Another snapshot. This has a complete implementation of thread ops and atomics of all sizes for all tier-1 platforms but the queue is pretty messy, and there's some outstanding cleanup.
Attachment #8911236 -
Attachment is obsolete: true
|
|
Reporter | |
Updated•7 years ago
|
Priority: P2 → P1
|
|
Reporter | |
Comment 3•7 years ago
|
||
Functionally complete and with test cases apart from the issue around atomic access to current_memory during a concurrent grow_memory: https://treeherder.mozilla.org/#/jobs?repo=try&revision=1148fff7492d327d5d2f6bf281603e19a18cf40a
|
|
Reporter | |
Comment 4•7 years ago
|
||
The patch set for that try run.
Attachment #8915685 -
Attachment is obsolete: true
|
|
Reporter | |
Updated•7 years ago
|
Depends on: wasm-bulkmem
|
|
Reporter | |
Comment 5•7 years ago
|
||
New patch set with some bug fixes and better test cases; new builds: https://treeherder.mozilla.org/#/jobs?repo=try&revision=cdca47678e191aaf81d8be5252c26b6ffbc49c1d
Attachment #8924132 -
Attachment is obsolete: true
|
|
Reporter | |
Comment 6•7 years ago
|
||
New queue, with fixes after reviews and rebasing. Artifacts here (even though the patch set does not look clean in this try build it is the same): https://treeherder.mozilla.org/#/jobs?repo=try&revision=a97f120a4a037a9954b3ce6be3c9013bd4040cf7
Attachment #8926293 -
Attachment is obsolete: true
|
|
Reporter | |
Comment 7•6 years ago
|
||
(metabug, no owner)
Assignee: lhansen → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3
|
||
Comment 8•6 years ago
|
||
This news item may be of interest ... it references this issue WebAssembly Threads ready to try in Chrome 70 (developers.google.com) https://news.ycombinator.com/item?id=18332991
|
||
Comment 9•6 years ago
|
||
Please implement it - it is the one last major item which keeps webassembly from beeing really useful.
|
||
Comment 10•5 years ago
|
||
Should this be marked as blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1477743 ?
|
|
||
Comment 11•4 years ago
|
||
please prioritize - Google shipped this enabled by default with Chrome 74 - release on 2019-04-23.
So exactly 3 months to go until Firefox lacks Chrome by a whole year when it comes to webassembly threads.
|
|
Reporter | |
Updated•4 years ago
|
Component: JavaScript Engine → Javascript: WebAssembly
|
|
Reporter | |
Comment 12•4 years ago
|
||
We're done here - the two remaining blockers aren't really blocking anything. \o/
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
|
||
Comment 13•4 years ago
|
||
I've completed the documentation on MDN about this; see https://github.com/mdn/sprints/issues/3428#issuecomment-655053796 for details.
Let me know if you think this needs anything else; thanks!
Keywords: dev-doc-needed → dev-doc-complete
You need to log in
before you can comment on or make changes to this bug.
Description
•