[release/10.0] Fix assertions generated by optCreateJumpTableImpliedAssertions#127003
Open
github-actions[bot] wants to merge 1 commit intorelease/10.0from
Open
[release/10.0] Fix assertions generated by optCreateJumpTableImpliedAssertions#127003github-actions[bot] wants to merge 1 commit intorelease/10.0from
github-actions[bot] wants to merge 1 commit intorelease/10.0from
Conversation
Member
|
PTAL @jakobbotsch This fell off my radar. Backporting the fix from #123240 |
github-actions
bot
added
the
area-CodeGen-coreclr
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Contributor
|
Will this be included in milestone 10.0.7 ? |
jakobbotsch
approved these changes
Apr 16, 2026
This was referenced Apr 16, 2026
Open
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
3 participants
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 #123240 to release/10.0
/cc @EgorBo
Customer Impact
The JIT compiler could make invalid assumptions regarding the
default:case inswitchstatements concerning the possible ranges of the checked variable. This could lead to incorrect constant folding and branch removal. The original bug reproduction is available here: #122254Regression
Regressed via #113998 JIT optimization.
Testing
A test is added.
Risk
Low
Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.