Closed
Bug 1585108
Opened 6 years ago
Closed 6 years ago
[BinAST] Make enterTaggedTuple faster
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla71
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: Yoric, Assigned: Yoric)
References
Details
Attachments
(1 file, 1 obsolete file)
|
Bug 1585108 - Reworking enterTaggedTuple to remove the need to lookup when we're not in a sum;r?arai
47 bytes,
text/x-phabricator-request
|
Details | Review |
No description provided.
| Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Priority: -- → P1
| Assignee | ||
Comment 2•6 years ago
|
||
In many cases, we call enterTaggedTuple in situations in which we already know that there is only one possible value, which ends up encoded on 0 bits in Context. This patch lets us entirely skip the lookup.
Pushed by dteller@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c56533544a3d
Reworking enterTaggedTuple to remove the need to lookup when we're not in a sum;r=arai
Comment 4•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Updated•6 years ago
|
Assignee: nobody → dteller
Updated•6 years ago
|
Attachment #9098538 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•