[compiler] Remove the optimized OSR code if deoptimizing at inside of loop
If the optimized code is deoptimized and the deoptimized exit offset is inside of the optimized OSR code related loop, the optimized OSR code is also out of date, remove the optimized OSR code, it will avoid hit the optimized OSR code and soon later deoptimization of the optimized OSR code. This CL will reduce deoptimization. E.g. Deoptimization of JetStream2 case navier-stokes function addFields is reduced from twice to once. Change-Id: I5bbf3039e916c3736b5b967d1f36b6ea90cfd40b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3648219Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Tao Pan <tao.pan@intel.com> Cr-Commit-Position: refs/heads/main@{#80826}
Showing
Please
register
or
sign in
to comment