[release/11.0] JIT: update impFixupStructReturnType to handle GT_RET_EXPR - #133051
Open
github-actions[bot] wants to merge 1 commit into
Open
[release/11.0] JIT: update impFixupStructReturnType to handle GT_RET_EXPR#133051github-actions[bot] wants to merge 1 commit into
GT_RET_EXPR#133051github-actions[bot] wants to merge 1 commit into
Conversation
Fixes #130135 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c85aeea6-fddf-4696-b29d-c0cf7619fb37
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
EgorBo
approved these changes
Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #132986 to release/11.0
/cc @AndyAyersMS
Customer Impact
Reported via issue #130135
Regression
This has been broken since .NET 8. In release it causes an AV in the JIT.
Testing
Verified on repro case
Risk
Low, point fix for a rarely occurring case.