• Jakob Kummerow's avatar
    Fix IC handler cache clearing for JSBuiltinsObject · c177910d
    Jakob Kummerow authored
    The clearing mechanism relies on comparing the cached handler with the installed handler. If we try to preserve monomorphism by pretending that the IC was in uninitialized state, then it will go premonomorphic first, which means on the next miss there's no installed handler available to compare against. Instead, pretend it was premonomorphic, so the comparison will happen right away, will fail as it should, and the cached handler will be cleared.
    
    Thanks to Weiliang for starting the investigation that led to this.
    
    R=verwaest@chromium.org
    
    Review URL: https://codereview.chromium.org/730383002
    
    Cr-Commit-Position: refs/heads/master@{#25394}
    c177910d
Name
Last commit
Last update
..
arm Loading commit data...
arm64 Loading commit data...
ia32 Loading commit data...
mips Loading commit data...
mips64 Loading commit data...
ppc Loading commit data...
x64 Loading commit data...
x87 Loading commit data...
access-compiler.cc Loading commit data...
access-compiler.h Loading commit data...
call-optimization.cc Loading commit data...
call-optimization.h Loading commit data...
handler-compiler.cc Loading commit data...
handler-compiler.h Loading commit data...
ic-compiler.cc Loading commit data...
ic-compiler.h Loading commit data...
ic-inl.h Loading commit data...
ic-state.cc Loading commit data...
ic-state.h Loading commit data...
ic.cc Loading commit data...
ic.h Loading commit data...
stub-cache.cc Loading commit data...
stub-cache.h Loading commit data...