Remove flag for large arraybuffers in FF92 or later
Categories
(Core :: JavaScript Engine, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: lth, Assigned: jandem)
References
Details
Attachments
(4 files)
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
Bug 1703508 part 3 - Replace TypedArrayObject::maxByteLength() with MaxByteLength constant. r?rhunt!
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details |
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.
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
This shipped in Firefox 89, more than a year ago.
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D165027
Assignee | ||
Comment 3•2 years ago
|
||
Depends on D165028
Assignee | ||
Comment 4•2 years ago
|
||
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
Comment 6•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e043263b196a
https://hg.mozilla.org/mozilla-central/rev/3d9440116a22
https://hg.mozilla.org/mozilla-central/rev/597b8afe7562
https://hg.mozilla.org/mozilla-central/rev/729e4c4ef7c8
Description
•