• alph's avatar
    Eliminate no_frame_range data · 8d55da38
    alph authored
    It was supposed to be used by the CPU profiler. But as long as
    these ranges are not built when profiler is not running, once
    the profiler is started there're no ranges for already compiled
    functions. So basically this code never worked.
    
    As long as now CPU profiler uses another approach this code is no
    longer needed.
    
    Review URL: https://codereview.chromium.org/1376333003
    
    Cr-Commit-Position: refs/heads/master@{#31056}
    8d55da38
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...