Closed Bug 1635115 Opened 5 years ago Closed 5 years ago

Initialize "input" ImmutableScriptFlags in SharedContext

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox78 --- fixed

People

(Reporter: tcampbell, Assigned: tcampbell)

References

Details

Attachments

(2 files)

Ensure that all the "input" flags are initialized in SharedContext constructor. This provides a more consistent definition throughout frontend.

This removes all other locations through the frontend where these flags would
be set. The transitive options are applied to all SharedContext, while the
non-transitive flags are only applied to top-level (non-function)
SharedContext. Also update frontend to stop reading these CompileOptions
flags directly and instead rely on the SharedContext::immutableFlags.

Depends on D73695

As we progress towards Stencil, these "prepare" abstractions make less sense
as their original purpose was to allocate GC-things.

Depends on D73696

Severity: -- → N/A
Pushed by tcampbell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f19716c861d3 Initialize "input" ImmutableFlags in SharedContext constructor. r=mgaudet https://hg.mozilla.org/integration/autoland/rev/6932cdaa9e76 Inline SourceAwareCompiler::prepareScriptParse and friends. r=mgaudet
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: