• 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
..
OWNERS Loading commit data...
assembler-x87-inl.h Loading commit data...
assembler-x87.cc Loading commit data...
assembler-x87.h Loading commit data...
builtins-x87.cc Loading commit data...
code-stubs-x87.cc Loading commit data...
code-stubs-x87.h Loading commit data...
codegen-x87.cc Loading commit data...
codegen-x87.h Loading commit data...
cpu-x87.cc Loading commit data...
deoptimizer-x87.cc Loading commit data...
disasm-x87.cc Loading commit data...
frames-x87.cc Loading commit data...
frames-x87.h Loading commit data...
interface-descriptors-x87.cc Loading commit data...
lithium-codegen-x87.cc Loading commit data...
lithium-codegen-x87.h Loading commit data...
lithium-gap-resolver-x87.cc Loading commit data...
lithium-gap-resolver-x87.h Loading commit data...
lithium-x87.cc Loading commit data...
lithium-x87.h Loading commit data...
macro-assembler-x87.cc Loading commit data...
macro-assembler-x87.h Loading commit data...
simulator-x87.cc Loading commit data...
simulator-x87.h Loading commit data...