[release/8.0-staging] [mono] Workaround MSVC miscompiling sgen_clz#114904
Merged
akoeplinger merged 1 commit intorelease/8.0-stagingfrom Apr 23, 2025
Merged
Conversation
After the recent VS upgrade from 17.12.5 to 17.13.2 we started seeing access violations in the mono-aot-cross.exe when targetting wasm. We tracked it down to sgen_clz being miscompiled, we can workaround the compiler bug by switching from ternary condition to if/else.
BrzVlad
approved these changes
Apr 22, 2025
This was referenced Apr 22, 2025
Open
Member
|
No-op change to workaround compiler bug, tell mode, applying servicing-approved. |
Member
|
/ba-g unrelated CI timeouts |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #114786 to release/8.0-staging
/cc @akoeplinger
Customer Impact
Newer version of MSVC miscompiles a certain function in the mono runtime, leading to crashes.
Regression
Yes, due to infrastructure update bringing in new VS/MSVC.
Testing
Manual testing.
Risk
Low, this is a no-op change to workaround a compiler bug.