• bmeurer's avatar
    [turbofan] Split JSGlobalObjectSpecialization into separate class. · 4eb41ba7
    bmeurer authored
    The JSNativeContextSpecialization class is getting rather huge with all
    the stuff related to property and element access going in. Splitting off
    the global object related stuff into JSGlobalObjectSpecialization seems
    like a natural separation, especially since the global object
    specialization is sort of separate issue anyway.  This is neutral
    functionality- and performance-wise.
    
    R=jarin@chromium.org
    BUG=v8:4470
    LOG=n
    
    Review URL: https://codereview.chromium.org/1417043006
    
    Cr-Commit-Position: refs/heads/master@{#31748}
    4eb41ba7
Name
Last commit
Last update
benchmarks Loading commit data...
build Loading commit data...
docs Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
Makefile.nacl Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...