Stop updating DOMExpandoGeneration IC stub fields
Categories
(Core :: JavaScript Engine: JIT, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
References
Details
Attachments
(3 files)
We have an optimization to update existing Baseline/Ion IC stubs if only the DOMExpandoGenerationField field changed. Unfortunately this complicates Warp transpiler support for these DOM proxies (see bug 1668831) and we don't do this for any other IC stubs.
evilpie added some logging and we almost never update stubs on popular websites and speedometer. There's also some risk of updating the same stub repeatedly in pathological cases and that could be worse than not updating at all.
| Assignee | ||
Comment 1•5 years ago
|
||
Updating stubs complicates Warp transpiler support for DOM proxies and doesn't
actually show up much on websites.
| Assignee | ||
Comment 2•5 years ago
|
||
The Ion CacheIR implementation can now bake in the generation again instead of
loading it from the stub.
Depends on D92608
Comment 3•5 years ago
|
||
When looking at the old patch in bug 1329195 I also noticed this change: https://hg.mozilla.org/mozilla-central/rev/80e4fe7ff7cb#l5.37 Not sure if that should be reverted as well.
| Assignee | ||
Comment 4•5 years ago
|
||
Comment 6•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/d9ca15f17655
https://hg.mozilla.org/mozilla-central/rev/ca23b81385d4
https://hg.mozilla.org/mozilla-central/rev/48b632dabf39
Description
•