• clemensh's avatar
    Fix CHECK_OP implementation in Release builds · 4dcbe86e
    clemensh authored
    In this particular case, we just did a (lhs)op(rhs), ignoring the case
    that lhs and rhs might have different signedness.
    This CL changes that to use the proper Cmp##op##Impl implementation,
    which does two comparisions for signed-vs-unsigned checks, avoiding
    compiler errors.
    
    R=ishell@chromium.org
    
    Review-Url: https://codereview.chromium.org/2642383002
    Cr-Commit-Position: refs/heads/master@{#42566}
    4dcbe86e
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...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...