Can we make CompileOptions return us a JSScript::ImmutableFlags
Categories
(Core :: JavaScript Engine, task, P2)
Tracking
()
People
(Reporter: mgaudet, Assigned: caroline)
References
Details
Attachments
(3 files)
This will avoid having to copy all sorts of things individually and generally provide a route for us to share with Smoosh.
Comment 1•5 years ago
•
|
||
Probably worth sorting these flags to the start of the enum just for clarity. (Some of the ImmutableFlags are inputs, while the rest are only outputs).
Reporter | ||
Comment 2•5 years ago
|
||
Should reorder these flags into:
[Input Flags]
[Parser Flags]
[Emitter Flags]
See CheckFlagsOnDelazification
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Pushed by mgaudet@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e3fffbd8245f Move ImmutableFlags for SharedStencil.h. r=mgaudet
Assignee | ||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
bugherder |
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
Depends on D64449
Pushed by mgaudet@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/edb67faa4068 Move setFlags with boolean logic into SharedStencil.h r=mgaudet https://hg.mozilla.org/integration/autoland/rev/dd11011dd49a Pass individual input flags as an ImmutableFlags to JSScript::Create. r=mgaudet
Comment 9•5 years ago
|
||
bugherder |
Assignee | ||
Comment 10•5 years ago
|
||
Initially, we wanted to have CompileOptions contain a ImmutableScriptFlags, so instead of having 3 separate input flags within CompileOptions we would have one representation for all input flags and use that representation of those flags throughout the vm. In practice, this was a harder problem because CompileOptions lives within the js/public directory and SharedStencil within js/src/vm.
Comment 11•5 years ago
|
||
Even if we leave CompileOptions alone for the reasons you state, we should be able to remove uses of it from within the parser/bce themselves.
Updated•5 years ago
|
Reporter | ||
Comment 12•5 years ago
|
||
We marked this one as leave-open because we split the landing: Can we resolve fixed now, or is there more patches incoming here?
Assignee | ||
Comment 13•5 years ago
|
||
This patch as stated is fixed, the more robust solution is to come. Those patches will be attached to other bugs elsewhere in the tree.
Updated•5 years ago
|
Description
•