Skip to content

Fix behavior of (uint)val in Mono to saturating behavior #100368

Description

@khushal1996

This issue is created to track the discussion in the comment --> #97529 (comment)
PR #97529 changes the behavior of floating point to integer conversions on x86/x64. It allows the conversions to follow saturating behavior which .NET wants to standardize on.

Link to the failing build --> https://github.com/dotnet/runtime/pull/97529/checks?check_run_id=23012453843

@fanyang-mono for tracking this issue.

Activity

  1. ghost added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Mar 27, 2024
  2. removed
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Mar 29, 2024
  3. tannergooding commented on Mar 31, 2024

    @tannergooding
    Member

    Just noting that this applies to all floating point -> integer conversions, they should all saturate under the new behavior we're standardizing against.

  4. added this to the 9.0.0 milestone on Jun 14, 2024
  5. removed
    untriagedNew issue has not been triaged by the area owner
    on Jun 21, 2024
  6. modified the milestones: 9.0.0, Future on Aug 8, 2024
  7. removed their assignment
    on Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions