Closed Bug 1602114 Opened 5 years ago Closed 5 years ago

Hoist ScriptSourceObject to ParseInfo

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: mgaudet, Assigned: mgaudet)

References

Details

Attachments

(4 files)

Currently the ScriptSourceObject is allocated deep inside of BytecodeCompiler (sometimes).

We should put ScriptSourceObject into ParseInfo. It's a better home for it.

Longer term, once stencil is done, we will no longer even need the ScriptSourceObject in the parser; currently the ScriptSourceObject is mostly used in the front end to create JSScript/LazyScripts.

Priority: -- → P3
Blocks: 1598714
Depends on: 1604558
Assignee: nobody → mgaudet
Status: NEW → ASSIGNED
Pushed by mgaudet@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6a14a4d4ba12 Don't pass parameterListEnd to CreateScriptSourceObject r=tcampbell https://hg.mozilla.org/integration/autoland/rev/f27c0adfc0d7 Root ScriptSourceObject inside of ParseInfo r=tcampbell https://hg.mozilla.org/integration/autoland/rev/869b3fe541d5 Use ParseInfo::sourceObject instead of the newly created script's sourceObject r=tcampbell https://hg.mozilla.org/integration/autoland/rev/85e35b7ab299 Remove sourceObjectOut param from CompileGlobalScript r=tcampbell
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: