Closed Bug 1675962 Opened 4 years ago Closed 3 years ago

Centralize LifoAlloc for initial stencil and delazifications in CompilationInfoVector

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED
85 Branch
Tracking Status
firefox85 --- fixed

People

(Reporter: arai, Assigned: arai)

References

Details

Attachments

(5 files)

there can be thousands of delazifications stored into CompilationInfoVector, and
allocation/free cost of LifoAlloc inside CompilationStencil in delazifications isn't negligible.

moving LifoAlloc to CompilationInfo and reusing initial stencil's LifoAlloc from delazification improves the performance.

These methods will be modified to take CompilationInput and CompilationStencil
separately in later patch.

Depends on D97114

Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/aa2f2b8408ee
Part 1: Make CompilationInfo methods static. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/3945960193ea
Part 2: Take CompilationInput and CompilationStencil separately. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/1d97945897ad
Part 3: Use CompilationStencil as delazifications vector element. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/63179c48aedc
Part 4: Add cache for CompilationAtomCache for delazifications. r=tcampbell
https://hg.mozilla.org/integration/autoland/rev/322ee18b6f51
Part 5: Move LifoAlloc to CompilationInfo and CompilationInfoVector, to share between all delazification. r=tcampbell
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: