[all-commits] [llvm/llvm-project] 2bfd7a: [TTI][X86] getMinMaxCost - use existing float minn...

[Simon Pilgrim via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 2bfd7a07b39c756fd857651fe827a46b7bd9af14
      https://github.com/llvm/llvm-project/commit/2bfd7a07b39c756fd857651fe827a46b7bd9af14
  Author: Simon Pilgrim <llvm-dev at redking.me.uk>
  Date:   2023-04-13 (Thu, 13 Apr 2023)

  Changed paths:
    M llvm/lib/Target/X86/X86TargetTransformInfo.cpp
    M llvm/test/Analysis/CostModel/X86/intrinsic-cost-kinds.ll
    M llvm/test/Analysis/CostModel/X86/reduce-fmax.ll
    M llvm/test/Analysis/CostModel/X86/reduce-fmin.ll

  Log Message:
  -----------
  [TTI][X86] getMinMaxCost - use existing float minnum/maxnum intrinsic cost values instead of maintaining a duplicate cost table

Without fastmath (nnan) flags, minnum/maxnum must perform isnan handling as well as fmin/fmax - meaning the costs are notably higher, this is correctly handled in getIntrinsicInstrCost but was missing from the getMinMaxCost cost tables (which assumed fastmath).

Followup to 63c3895327839ba5b57f5b99ec9e888abf976ac6 which handled the integer cases