Closed
Bug 1116773
Opened 10 years ago
Closed 3 years ago
BaldrMonkey: Support addresses with scaled indices
Categories
(Core :: JavaScript: WebAssembly, enhancement, P5)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: sunfish, Unassigned)
References
(Blocks 1 open bug)
Details
Bug 986981 is adding support for folding constant offsets into addresses. For x64 at least, we can also support scaled-index addressing in the same way, by increasing the size of the guard region.
Comment 1•10 years ago
|
||
Heh, yeah, for a while Odin mmap'd 35gb. My only concern is the recent issues we've seen with OSes capping virtual address space far below the 47-bit theoretical limit. Lars already added a mitigation for this:
http://hg.mozilla.org/mozilla-central/diff/9756bf697be4/js/src/vm/SharedArrayObject.cpp#l1.13
so we might need to extend it to normal asm.js array buffers (since it will be so much easier to hit).
Comment 2•8 years ago
|
||
It seems like it would require matching JS patterns, and it doesn't seem to be planned for wasm as far as i can see. That being said, this could probably be made as part of the EEA or something, so let's keep it.
Blocks: wasm-perf
Priority: -- → P5
Comment 3•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Updated•6 years ago
|
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Updated•5 years ago
|
Component: JavaScript Engine: JIT → Javascript: WebAssembly
Comment 4•5 years ago
|
||
We won't do this for asm.js but we might still want to do it for wasm.
Summary: OdinMonkey: Support addresses with scaled indices → BaldrMonkey: Support addresses with scaled indices
Updated•4 years ago
|
Assignee: sunfish → nobody
Status: REOPENED → NEW
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago → 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•