Remove pn_op from ParseNode
Categories
(Core :: JavaScript Engine, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: khyperia, Assigned: khyperia)
References
Details
Attachments
(3 files)
We're surprisingly close to getting this to happen.
I'll split the patch into three parts:
- Misc. cleanup (some NameNode changes, tiny change to True/False/Undefined/NullExpr, etc.)
- Function call cleanup.
- Deleting pn_op and refactoring all the ParseNode constructors/FullParseHandler/etc. to not provide opcodes.
Point 2 is a little weird, because I'll be adding a CallNode that contains a JSOp field. This is because there are a lot of different types of calls, and those are currently encoded into JSOp (for example, CALL, SPREADCALL, NEW, SPREADNEW, SUPERCALL, SPREADSUPERCALL, the list goes on and on). I could make a new enum that corresponds basically 1-to-1 with the JSOp items, and make a mapping function, but... really, what's the point at that point.
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Depends on D24409
Assignee | ||
Comment 3•6 years ago
|
||
Depends on D24410
Comment 4•6 years ago
|
||
Backed out for bustages in ParseNode.h
Push with failure: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&revision=8c405aa4467dfeb34b9df7e875c1584ed6f6a938
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=235272394&repo=autoland&lineNumber=5157
Backout: https://hg.mozilla.org/integration/autoland/rev/c99b0f4470527c183d90c1e7191a08e4933ad1ac
Comment 7•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/2bf248bc4f3b
https://hg.mozilla.org/mozilla-central/rev/4011496a13a9
https://hg.mozilla.org/mozilla-central/rev/d9660cff2091
Assignee | ||
Updated•6 years ago
|
Description
•