[all-commits] [llvm/llvm-project] f4ce80: ValueTracking: Handle minimumnum and maximumnum in...

[Matt Arsenault via All-commits]

  Branch: refs/heads/users/arsenm/valuetracking/handle-minimumnum-maximumnum-computeKnownFPClass
  Home:   https://github.com/llvm/llvm-project
  Commit: f4ce80771ff0bd5cc5cf86b8f38ab42ebc1fd697
      https://github.com/llvm/llvm-project/commit/f4ce80771ff0bd5cc5cf86b8f38ab42ebc1fd697
  Author: Matt Arsenault <Matthew.Arsenault at amd.com>
  Date:   2025-05-06 (Tue, 06 May 2025)

  Changed paths:
    M llvm/lib/Analysis/ValueTracking.cpp
    M llvm/test/Transforms/Attributor/nofpclass-minimumnum-maximumnum.ll
    M llvm/unittests/Analysis/ValueTrackingTest.cpp

  Log Message:
  -----------
  ValueTracking: Handle minimumnum and maximumnum in computeKnownFPClass

For now use the same treatment as minnum/maxnum, but these should
diverge. alive2 seems happy with this, except for some preexisting bugs
with weird denormal modes.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications