mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-27 04:38:02 +00:00
7d83d7c31e
The purpose here is to allow wasm memories to use up to 65534 pages of memory on 64-bit systems, if the underlying ArrayBuffer / SharedArrayBuffer supports it. (The remaining two pages remain out of bounds until we can make the bounds checking limit 64 bits wide, and some other things.) As the max value of the heap limit field is 65536, this should unlock memories above 2GB for all users who do not insist on actually allocating all 4GB. The changes here are: * Parameterize everything properly: Get rid of hardcoded UINT32_MAX and INT32_MAX and similar where that is possible. Some remain; comments have been added. * Add guards for asm.js to remain at heap limit INT32_MAX forever * Add guard for grow() methods to enforce the limit separately from arraybuffer code * Add test cases and test infrastructure * Clean up some transitional things that are no longer required, now that the underlying arraybuffer code is stable Some parameters are turned into function calls now, but may become constants again later. Differential Revision: https://phabricator.services.mozilla.com/D96602
An explanation of the Firefox Source Code Directory Structure and links to
project pages with documentation can be found at:
https://firefox-source-docs.mozilla.org/contributing/directory_structure.html
For information on how to build Firefox from the source code and create the patch see:
https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
If you have a question about developing Firefox, and can't find the solution
on https://firefox-source-docs.mozilla.org/, you can try asking your question on Matrix at chat.mozilla.org in `Introduction` (https://chat.mozilla.org/#/room/#introduction:mozilla.org) channel.
Nightly development builds can be downloaded from:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://www.mozilla.org/firefox/channel/desktop/#nightly
Keep in mind that nightly builds, which are used by Firefox developers for
testing, may be buggy.