New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 749511 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue v8:7881
Owner:
Closed: Dec 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature

Blocking:
issue 729768



Sign in to add a comment

WebAssembly should support full 4GiB memories on 64-bit

Project Member Reported by titzer@chromium.org, Jul 27 2017

Issue description

V8 and Chromium limit the maximum size of array buffers. V8 in particular limits the size of WebAssembly memories due to the underlying array buffer size limitation. These limitations should be restricted so that WebAssembly programs can use the full 4GiB memory.
 

Comment 1 by titzer@chromium.org, Jul 27 2017

Blocking: 729768

Comment 2 by titzer@chromium.org, Jul 27 2017

Preliminary assignment to eholk@, since he is doing all of the trap handler work, which deals with virtual memory underneath. Reassign if necessary.
Cc: jsc...@chromium.org
+justin

Comment 4 by jsc...@chromium.org, Jul 27 2017

Cc: -jsc...@chromium.org palmer@chromium.org

Comment 5 by eholk@chromium.org, Jul 27 2017

We'll need to make sure the test case introduced here works: https://chromium-review.googlesource.com/c/487047/

On x64 at least, we sign extend large constants and end up treating offsets above 2GiB as negative numbers.
Mergedinto: v8:7881
Owner: titzer@chromium.org
Status: Duplicate (was: Assigned)

Sign in to add a comment