Closed
Bug 1677260
Opened 4 years ago
Closed 4 years ago
Directly use TaggedParserAtomIndex in ObjLiteral code
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
85 Branch
| Tracking | Status | |
|---|---|---|
| firefox85 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(1 file)
No description provided.
|
Assignee | |
Comment 1•4 years ago
|
||
Now ParserAtom can be referred by single uint32_t data, and we don't have to
store ParserAtom pointer inside ObjLiteralWriter.
Previously the number of atoms referred from object literal was limited to
24-bit, in order to pack opcode + atom in 32-bit, but the limitation is removed,
and now atom always use 32-bit, separated from opcode.
Depends on D99050
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/e55e374892fe
Directly use TaggedParserAtomIndex in ObjLiteral code. r=nbp
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox85:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•