• Mythri A's avatar
    Set bytecode budget to interrupt_budget when allocating feedback vector · 443721bd
    Mythri A authored
    We use the same interrupt to both allocate feedback vectors and
    for updating the profiler ticks. If there is a feedback vector already
    available, we just increment the profiler ticks that we use to mark
    for optimizing function. Calling JSFunction::EnsureFeedbackVector
    allocates a feedback vector, but doesn't reset the budget, so we
    optimize much earlier than expected. This is currently only a problem
    with %PrepareFunctionForOptimize that doesn't reset the budget. Other
    code paths do also reset the interrupt budget.
    
    Bug: chromium:10243
    Change-Id: I611a9202e5e71077bf897def5959bcfe11b8fdf4
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2064980
    Commit-Queue: Mythri Alle <mythria@chromium.org>
    Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#66426}
    443721bd
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...