[wasm] Update bailout counters in liftoff
When Liftoff bails out, the function ExecuteLiftoffCompilation performs an early return before updating the "counters" data structure with the bailout reason. The early return was introduced in https://chromium-review.googlesource.com/c/v8/v8/+/2423710. We should just drop it again, as there is another "if (did_bailout()) return" right after updating the counters. Bug: v8:11259 Change-Id: Ia7f72c3a7eda4252a5a4450646427edb26130996 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2584880 Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#71713}
This commit is contained in:
parent
8ba4bcea01
commit
2b9a4d9a72
@ -4271,10 +4271,7 @@ WasmCompilationResult ExecuteLiftoffCompilation(
|
||||
dead_breakpoint);
|
||||
decoder.Decode();
|
||||
LiftoffCompiler* compiler = &decoder.interface();
|
||||
if (decoder.failed()) {
|
||||
compiler->OnFirstError(&decoder);
|
||||
return WasmCompilationResult{};
|
||||
}
|
||||
if (decoder.failed()) compiler->OnFirstError(&decoder);
|
||||
|
||||
if (counters) {
|
||||
// Check that the histogram for the bailout reasons has the correct size.
|
||||
|
Loading…
Reference in New Issue
Block a user