Closed Bug 1728565 Opened 3 years ago Closed 3 years ago

Move TypedArray and ArrayBuffer allocation out of the generic allocation code

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED FIXED
94 Branch
Tracking Status
firefox94 --- fixed

People

(Reporter: jandem, Assigned: jandem)

References

Details

Attachments

(4 files)

The generic allocation path is a lot simpler than before, but it still has some branching for objects that store data inline (typed arrays and array buffers) because this affects the number of fixed slots.

If we move allocation of these objects out of there we can turn that ClassCanHaveFixedData check into an assertion.

Attachment #9239125 - Attachment description: Bug 1728565 part 2 - Use ArrayBuffer arena for more ArrayBuffer objects. r?sfink! → Bug 1728565 part 2 - Use ArrayBuffer arena for all ArrayBuffer objects. r?sfink!
Pushed by jdemooij@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7ea3c57fa362 part 1 - Move ArrayBuffer allocation out of the generic allocation code. r=sfink https://hg.mozilla.org/integration/autoland/rev/0d17023ae58e part 2 - Use ArrayBuffer arena for all ArrayBuffer objects. r=sfink https://hg.mozilla.org/integration/autoland/rev/68c8333149ed part 3 - Move TypedArray allocation out of the generic allocation code. r=sfink https://hg.mozilla.org/integration/autoland/rev/706403fcb982 part 4 - Remove support for objects with fixed data from the generic allocation path. r=sfink
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: