Closed
Bug 1667615
Opened 4 years ago
Closed 4 years ago
Fold GlobalHelperThreadState::finishModuleParseTask into finishSingleParseTask
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
83 Branch
Tracking | Status | |
---|---|---|
firefox83 | --- | fixed |
People
(Reporter: tcampbell, Assigned: arai)
References
Details
Attachments
(1 file)
The finishModuleParseTask
relies on the global js::UseOffThreadParseGlobal
method instead of checking CompileOptions of the task. This makes it harder to mix stencil and script XDR modes in the browser.
If we combine the finishModuleParseTask
with finishSingleParseTask
which still has access to the task, we can check options instead.
Additionally, the module->fixEnvironmentsAfterRealmMerge();
code can probably go into the mergeRealms block https://searchfox.org/mozilla-central/rev/0eebca3c33b7999bfd090672e6c6dde96ae89616/js/src/vm/HelperThreads.cpp#1884-1911
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•4 years ago
|
||
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/a0392a47a8f4
Move module handling from GlobalHelperThreadState::finishModuleParseTask to GlobalHelperThreadState::finishSingleParseTask. r=tcampbell
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•