Closed Bug 1808881 Opened 1 year ago Closed 1 year ago

Remove JSContext from CompilationInput initialization

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: arai, Assigned: arai)

References

Details

Attachments

(5 files)

No description provided.

There are some r+ patches which didn't land and no activity in this bug for 2 weeks.
:arai, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.

Flags: needinfo?(tcampbell)
Flags: needinfo?(arai.unmht)
Flags: needinfo?(tcampbell)
Flags: needinfo?(arai.unmht)
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/834979bd7298
Part 1: Remove JSContext parameter from FormatIntroducedFilename. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/0645eb4a144a
Part 2: Remove JSContext parameter from ScriptSource::initFromOptions. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/cd4165f39946
Part 3: Remove JSContext parameter from CompilationInput initialization. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/7fb5bf792934
Part 4: Remove JSContext parameter from SourceAwareCompiler initialization. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/73f8ed526ed5
Part 5: Directly use FrontendContext in CompilationInput::initForSelfHostingGlobal. r=tcampbell
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: