• 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
..
base Loading commit data...
compiler Loading commit data...
compiler-dispatcher Loading commit data...
heap Loading commit data...
interpreter Loading commit data...
libplatform Loading commit data...
wasm Loading commit data...
zone Loading commit data...
BUILD.gn Loading commit data...
DEPS Loading commit data...
cancelable-tasks-unittest.cc Loading commit data...
char-predicates-unittest.cc Loading commit data...
counters-unittest.cc Loading commit data...
eh-frame-iterator-unittest.cc Loading commit data...
eh-frame-writer-unittest.cc Loading commit data...
locked-queue-unittest.cc Loading commit data...
object-unittest.cc Loading commit data...
register-configuration-unittest.cc Loading commit data...
run-all-unittests.cc Loading commit data...
source-position-table-unittest.cc Loading commit data...
test-utils.cc Loading commit data...
test-utils.h Loading commit data...
unicode-unittest.cc Loading commit data...
unittests.gyp Loading commit data...
unittests.isolate Loading commit data...
unittests.status Loading commit data...
value-serializer-unittest.cc Loading commit data...