76a817e03a
This fixes a TODO about atomics and memory64 and removes the explicit CHECK that checks for the unsupported situation. Similar to other memory accesses, the memory index is supposed to be a 64-bit value if memory64 is being used. The bounds checking implementation in Liftoff and TurboFan is shared with non-atomic memory accesses, so this is already prepared for memory64. We only need to fix the expected type in the function body decoder, and prepare the assembler for 64-bit values. R=jkummerow@chromium.org Bug: v8:13636, v8:10949 Change-Id: I210ac488bd2bb1cb141e16597ca62d3fb27cad3b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4191767 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#85525} |
||
---|---|---|
.. | ||
benchmarks | ||
bigint | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
fuzzilli | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
test262 | ||
torque | ||
unittests | ||
wasm-api-tests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn | ||
OWNERS |