Closed Bug 1732356 Opened 4 years ago Closed 4 years ago

Tidy up WasmIonCompile in preparation for memory64

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
95 Branch
Tracking Status
firefox95 --- fixed

People

(Reporter: lth, Assigned: lth)

References

Details

Attachments

(2 files)

We should reorg very slightly and comment somewhat copiously around heap access in WasmIonCompile to set us up for sanely changing things for memory64. Right now the logic for bounds and alignment check optimization is very tangled and in general there is little documentation about this.

Move SIMD memory access implementations into a "memory access" part of
WasmIonCompile, to keep all memory access operations together.

Factor WasmIonCompile memory access logic to make it clearer, and
comment.

Document the heap structure + bounds checking logic generally. (A
very small amount of documentation pertains to memory64, I judged that
this was probably OK. More documentation will be added when memory64
lands.)

No functional changes whatsoever are intended.

Pushed by lhansen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f1923637734f Bounds checking comments + some ion cleanup. r=rhunt
Keywords: leave-open
Attachment #9243651 - Attachment description: WIP: Bug 1732356 - Document some memory functions better → Bug 1732356 - Document some memory functions better. r?yury
Keywords: leave-open
Pushed by lhansen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/64afb5141f63 Document some memory functions better. r=yury
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: