Bug 1518210 - Wasm: Rename WASM_HUGE_MEMORY to WASM_SUPPORTS_HUGE_MEMORY. r=lth

To highlight that WASM_HUGE_MEMORY doesn't imply we are using huge memory, this
commit renames the #define.

Most usages of WASM_HUGE_MEMORY are not updated, as they will be removed in
later commits.

Differential Revision: https://phabricator.services.mozilla.com/D41867

--HG--
extra : moz-landing-system : lando
This commit is contained in:
Ryan Hunt 2019-08-30 02:33:13 +00:00
parent bf066f7629
commit 5d32d4c9b7
2 changed files with 3 additions and 3 deletions

View File

@ -7,7 +7,7 @@
# Some huge-mapping optimization instead of bounds checks on supported
# platforms.
if CONFIG['JS_CODEGEN_X64'] or CONFIG['JS_CODEGEN_ARM64']:
DEFINES['WASM_HUGE_MEMORY'] = True
DEFINES['WASM_SUPPORTS_HUGE_MEMORY'] = True
# Enables CACHEIR_LOGS to diagnose IC coverage, and
# Structured spewer for diagnostics

View File

@ -34,9 +34,9 @@ using namespace js::wasm;
using mozilla::IsPowerOfTwo;
using mozilla::MakeEnumeratedRange;
// We have only tested WASM_HUGE_MEMORY on x64 and arm64.
// We have only tested huge memory on x64 and arm64.
#if defined(WASM_HUGE_MEMORY)
#if defined(WASM_SUPPORTS_HUGE_MEMORY)
# if !(defined(JS_CODEGEN_X64) || defined(JS_CODEGEN_ARM64))
# error "Not an expected configuration"
# endif