Commit f8787c11 authored by Ivica Bogosavljevic's avatar Ivica Bogosavljevic Committed by Commit Bot

MIPS64: Lower address space requirements in WasmMemoryTracker

Most MIPS64 processors have user space of 2^40 bytes. Therefore,
we need to lower the address space limit in WasmMemoryTracker
for this particular architecture.

Change-Id: Ic9945af7a15ecba7dfabfe996140941ada089b2a
Reviewed-on: https://chromium-review.googlesource.com/1079551Reviewed-by: 's avatarEric Holk <eholk@chromium.org>
Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@mips.com>
Cr-Commit-Position: refs/heads/master@{#53468}
parent 03c85c23
......@@ -101,7 +101,11 @@ bool WasmMemoryTracker::ReserveAddressSpace(size_t num_bytes) {
// Address space reservations are currently only meaningful using guard
// regions, which is currently only supported on 64-bit systems. On other
// platforms, we always fall back on bounds checks.
#if V8_TARGET_ARCH_64_BIT
#if V8_TARGET_ARCH_MIPS64
// MIPS64 has a user space of 2^40 bytes on most processors,
// address space limits needs to be smaller.
constexpr size_t kAddressSpaceLimit = 0x2000000000L; // 128 GiB
#elif V8_TARGET_ARCH_64_BIT
constexpr size_t kAddressSpaceLimit = 0x10000000000L; // 1 TiB
#else
constexpr size_t kAddressSpaceLimit = 0x80000000; // 2 GiB
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment