• Clemens Hammacher's avatar
    [Liftoff][ia32] Handle overflow in memory offset · a0e66bca
    Clemens Hammacher authored
    When generating a 64bit memory operation on ia32, we need to emit two
    operations, one at {offset+4}, one at {offset}. The computation
    {offset+4} can overflow, which is ok because
    1) it won't be used for code generation later, and
    2) the generated code will not be reached because the memory access is
       always out of bounds anyway.
    
    R=ahaas@chromium.org
    
    Bug: v8:7499, v8:6600
    Change-Id: Ia4660688c3291700c48efc201d15fc370b4dd854
    Reviewed-on: https://chromium-review.googlesource.com/939389Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#51604}
    a0e66bca
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.isolate Loading commit data...
d8_default.isolate Loading commit data...
default.isolate Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.isolate Loading commit data...