Use consistent script flags for BinAST lazy scripts
Categories
(Core :: JavaScript Engine, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox77 | --- | fixed |
People
(Reporter: tcampbell, Assigned: tcampbell)
References
Details
Attachments
(2 files)
There are a few issues in the BinAST frontend not being patched as changes to the normal parser were made. These patches fix some of them.
Assignee | ||
Comment 1•4 years ago
|
||
Lazy scripts generated by BinAST parser do not track their inner-functions or
their closed-over-binding info so remove misleading code. In the
finishLazyFunction code the pc_
is actually for parent and it is invalid
for us to use it here.
Assignee | ||
Comment 2•4 years ago
|
||
This fixes some issues that snuck in for flag initialization in the BinAST
frontend. These changes match LazyScriptCreationData::create behaviour now.
Also remove a redundant strict flag initialization from BCEScriptStencil that
was missed in Bug 1628111.
Depends on D72008
Pushed by tcampbell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/136080eee01b Use BaseScript::CreateRawLazy in the BinAST case. r=mgaudet https://hg.mozilla.org/integration/autoland/rev/acd35b5038b9 Fixup BinAST lazy script flag computation. r=mgaudet
Comment 4•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/136080eee01b
https://hg.mozilla.org/mozilla-central/rev/acd35b5038b9
Description
•