Closed Bug 1703508 Opened 3 years ago Closed 1 year ago

Remove flag for large arraybuffers in FF92 or later

Categories

(Core :: JavaScript Engine, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
110 Branch
Tracking Status
firefox110 --- fixed

People

(Reporter: lth, Assigned: jandem)

References

Details

Attachments

(4 files)

We keep the pref for large arraybuffers at least until FF92, in case something bad happens.

In FF92 or later we can remove it. The fallout of this will also be that some test cases will be updated, and some functions in the runtime can become constants again, and some MOZ_ASSERTS can therefore become static_asserts. ArrayBufferObject::maxBufferByteLength() and ArrayBufferObject::supportLargeBuffers are good places to start.

Summary: Remove flag for large arraybuffers in FF90 or later → Remove flag for large arraybuffers in FF92 or later
Assignee: lhansen → nobody
Status: ASSIGNED → NEW

This shipped in Firefox 89, more than a year ago.

Assignee: nobody → jdemooij
Status: NEW → ASSIGNED

This testing function is now equivalent to checking whether we're on a 64-bit platform
so it's technically redundant, but it's a bit more descriptive.

Depends on D165029

Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e043263b196a
part 1 - Remove pref for large ArrayBuffers. r=rhunt
https://hg.mozilla.org/integration/autoland/rev/3d9440116a22
part 2 - Replace maxBufferByteLength() with MaxByteLength constant. r=rhunt
https://hg.mozilla.org/integration/autoland/rev/597b8afe7562
part 3 - Replace TypedArrayObject::maxByteLength() with MaxByteLength constant. r=rhunt
https://hg.mozilla.org/integration/autoland/rev/729e4c4ef7c8
part 4 - Rename largeArrayBufferEnabled testing function to largeArrayBufferSupported. r=rhunt
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: