Fix BigInteger to double conversion rounding on s390x - #131491
Open
abhishekabhi73cc-design wants to merge 3 commits into
Open
Fix BigInteger to double conversion rounding on s390x#131491abhishekabhi73cc-design wants to merge 3 commits into
abhishekabhi73cc-design wants to merge 3 commits into
Conversation
abhishekabhi73cc-design
requested review from
steveisok and
vitek-karas
as code owners
July 28, 2026 20:16
|
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. |
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.
Summary
Fix the rounding mode used by the s390x
CDLGBRinstruction during BigInteger to double conversion in the Mono JIT.The CDLGBR instruction encodes the IEEE-754 rounding mode in its M3 field. The implementation was using M3 = 6 (round toward +infinity), which produced incorrect results for values that require round-to-nearest-even behavior.
This change updates the M3 field to 4, which corresponds to round to nearest with ties to even, matching the expected .NET floating-point conversion semantics.