Closed
Bug 1687634
Opened 5 years ago
Closed 5 years ago
Cleanup FindReservedWord
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
87 Branch
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
After bug 1687428, we use TaggedParserAtomIndex
almost everywhere, and
all reserved words are well-known atom.
So we don't have to look into the atom content, but just check the index.
Assignee | ||
Comment 1•5 years ago
|
||
WIP patch results in 2.4% improvement in parsemark
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D103546
Assignee | ||
Comment 3•5 years ago
|
||
Instead of looking into ParserAtomEntry content, compare tagged index against
well-known atoms.
visibility
parameters are removed because they're unused in practice.
Character-based FindReservedWord used by TokenStreamSpecific::identifierName is
kept, because replaing it with atom-index based one results in ~0.7% regression
across parsemark.
Depends on D103547
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/0883c747def3
Part 1: Remove unused JSLinearString variant of IsKeyword/FindReservedWord. r=nbp
https://hg.mozilla.org/integration/autoland/rev/1d18648713ad
Part 2: Add TaggedParserAtomIndex-specific variant of FindReservedWord. r=nbp
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0883c747def3
https://hg.mozilla.org/mozilla-central/rev/1d18648713ad
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox87:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•