27538aa361
Move the recently introduced extra check for 32-bit platforms so that it covers all code paths that would be hit by custom/future memory limit settings. Bug: chromium:1057094 Change-Id: I5e2217a24578ee82c7bfa753b7d5dcd3d00e1b7c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083300 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#66568}
15 lines
392 B
JavaScript
15 lines
392 B
JavaScript
// Copyright 2020 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Flags: --wasm-max-mem-pages=65536
|
|
|
|
try {
|
|
var __v_50189 = new WebAssembly.Memory({
|
|
initial: 65536
|
|
});
|
|
} catch (e) {
|
|
// 32-bit builds will throw a RangeError, that's okay.
|
|
assertTrue(e instanceof RangeError);
|
|
}
|