• Clemens Backes's avatar
    [wasm] Introduce separate limits for memory64 · b10bff90
    Clemens Backes authored
    This breaks up the existing {max_mem_pages()} method and the
    {kSpecMaxMemoryPages} and {kV8MaxWasmMemoryPages} constants into two
    versions for memory32 and memory64, respectively.
    
    For now, the limits are still the same.
    
    Some checks and clamping is moved to earlier places where we still have
    the information whether a memory is 32 or 64 bit.
    We also store that information in the WasmMemoryObject and use this for
    knowing the maximum for growing.
    
    This CL is not supposed to change any observable behaviour.
    
    R=jkummerow@chromium.org
    
    Bug: v8:10949
    Change-Id: Ieaca0596d1a24ef2746842954a75188494103eb2
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3782677Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
    Commit-Queue: Clemens Backes <clemensb@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#81960}
    b10bff90
wasm-objects.tq 7.95 KB