Closed Bug 1584649 Opened 6 months ago Closed 5 months ago

Small Standalone Bytecode Emitter Cleanups around GC thing requirements.

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: mgaudet, Assigned: mgaudet)

References

(Blocks 1 open bug)

Details

Attachments

(5 files)

No description provided.

Note, the deferred code paths are unused until we move publication -after- bytecode emission

Pushed by mgaudet@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/95fa040657ec
Support putting field initializers inside the LazyScriptCreationData r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/7414831ed19d
Eliminate function requirement in BytecodeEmitter::emitFunction r=tcampbell
Blocks: 1585196

I've ended up putting the 'fun' back in Bug 1583816 to get Part 1 landed. It requires the function when the JSScript is first created rather than when add the scopes to the JSScript.

Priority: -- → P1
Status: NEW → ASSIGNED
Pushed by mgaudet@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/82d9a4a318b3
Remove un-needed template parameter in EmitterScope r=tcampbell

This is subsequently used to allow BytecodeEmitter access to the ParseInfo,
so that the BytecodeEmitter can decide the vary its behviour depending on
the ParseInfo.

This allows the bytecode emitter to vary its code paths depending on whether
or not we are deferring GC object allocation.

Depends on D51010

Pushed by mgaudet@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1a8bbfa8377b
Provide bytecode compiler with access to the ParseInfo r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/ae7a806fdd91
Provide Bytecode Emitter access to ParseInfo r=tcampbell

Closing this one, will open a new bug if I find new fixes.

Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.