Investigate storing chunk metadata as a header at the start of the chunk
Categories
(Core :: JavaScript: GC, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox86 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
Details
Attachments
(3 files)
Currently we store all pre-chunk data as a trailer at the end of the chunk. This means the offset to this data depends on the size of the chunk. If we store it at the start then it becomes a constant. There are a bunch of hardcoded offsets like this defined in HeapAPI.h. It should also be possible have the compiler generate these for us.
Assignee | ||
Comment 1•4 years ago
|
||
This clears or sets every bit, taking care not to set trailing unused bits at the end of storage.
Assignee | ||
Comment 2•4 years ago
|
||
Previouly this used SpiderMonkey's BitArray, but that's not public. BitSet performs the same function.
Depends on D101775
Assignee | ||
Comment 3•4 years ago
|
||
This moves the chunk metadata to the start of the chunk and defines the data structures in the public header. This simplifies accessing this data and removes the need for hardcoded offsets.
Requesting review from jandem for JIT updates.
Depends on D101776
Updated•4 years ago
|
Updated•4 years ago
|
Comment 5•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/cc7e6feeb95a
https://hg.mozilla.org/mozilla-central/rev/496d47ff3fa1
https://hg.mozilla.org/mozilla-central/rev/43978ebfc7ac
Description
•