Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2026-05-21, Version 24.16.0 'Krypton' (LTS) #63263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v24.x
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
2026-05-21, Version 24.16.0 'Krypton' (LTS) #63263
Changes from 1 commit
cb67a92b39508b37d49f3be4d2f3493ac4057ef8457597d20ad9a29040ccfdedd43eff938af9bdb9497f332088fada3ce81fee2656b53efbca16ad85ee40d66c0012473fcc2b769efc0a869d2581bac1eaa1d8a99f3bc70736ed8ab267f6b7ce95afa71a4ac86d4f074739c4523f9275099ded5fa46c902faba666f37f7ef1a6e9f5dad616609c0137b1211fbe23b7567e0ac51684ab89705f629dd55406151999d73dbb9dd72df029b1966e04e2c9ef384fe9e2171185d83c2d202e2db4768850b4e0d3978afeac400d463ed78353c96ae1c58fe382f37f91f00cdab8126d1c70b4d58ba016331b1eb9edfb9ede06c405ff7bd9e3f218a4f6cd368b63c111cce47ea33d181623527646795db76314dacd2d6363887443b401090f2c22d3416b7280b9b95c41978f5c15e14e4d3ba0addc70ff44430c69da932fbdddf1f018637524ec2451bbfc13199c700f3841dfbfafdd355947f1ae3aa9938036bc6f698d828375a993b7fdd940fba9e8cd9890a94433e4ef7ffce9a3a190d0c9137cfb1fa9cd7e26200e86f013b7d0837d3913f5036750253c6e1e2915ca47ea6d59e7fb701a9552f4ea4953e720655c4798d169b5eaeeae75425d2e99da4dd86d142c5864f15c21a6085101dfe5924a0781e95570c7bd08ff6e097ee46c99edca02af1b5ca5ad09e17fe76f21c53e1036597e32c7c23db1c16e8c2bef413b59354bf414a4cb80e2adb3b6219b6a0f9000137e09c4d396ac2a9ccc95d97919ecb4d49900dc759a25fc84bf858404d3538ff86b1db13301962fe0cf1718bc391a07cf7cd206699bb02f5a93bded7188af1397d8c717476a7792f1aadd94f45b491788b3a4fc60c83f6233894a5556b151d00313e073b38b2b0bf86df15086553202ca0080cb91a9343be70ffa31a8eec9d4a44f49175b5304db9722c0c345c1ebd7f3a85eedeed4321e9239ea4f19a08726cd76d9c2428c4f44f50ac5bdca1e6a3f74a58b6378e2b2981ec476926cabb881ec12894200705a4f697c55a12dc44dafed454a506acf2a1735d0d19bd31a863f2ca42c828a7874341947eaa1e0bc8752b6036cc0414f3f21b3dc3fb6b3bfe35b881658ec8c6b9d14029b5c27704f68189b6026811File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Original commit message: [maglev] Fix throwing node inside eager inlining This commit refactors the exception handling logic to correctly identify and associate nodes with their respective `catch` blocks, even when multiple levels of inlining are involved. Previously, the check `!IsInsideTryBlock() && !is_eager_inline()` was insufficient to determine if catch block inside `CatchDetails` was already created. Specifically, consider the case where: 1. Function `bar` is non-eagerly inlined into `foo`. 2. `foo` contains a `catch` block. 3. `bar` calls `in_bar`, which is eagerly inlined. 4. A node within `in_bar` can `throw`. In this scenario, `is_eager_inline` would be true when compiling `in_bar`, leading to an incorrect assumption that the catch block didn't exist yet. This change addresses the issue by propagating a boolean value via `CatchDetails`. This boolean accurately indicates whether a `catch` block is present in the call chain, allowing for correct exception handling regardless of inlining depth or eagerness. Fixed: 417768368 Change-Id: Ic52f72f302b4dc644bdcad939addf98111bc525b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6563500 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#100380} Refs: v8/v8@657d8de PR-URL: #62784 Reviewed-By: Xuguang Mei <meixuguang@gmail.com>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.