[all-commits] [llvm/llvm-project] 1667fb: [InstCombine] add test with multiple uses of min/m...

[RotateRight via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 1667fbe65082a1daf757d090bd57450b4e595db4
      https://github.com/llvm/llvm-project/commit/1667fbe65082a1daf757d090bd57450b4e595db4
  Author: Sanjay Patel <spatel at rotateright.com>
  Date:   2021-04-09 (Fri, 09 Apr 2021)

  Changed paths:
    M llvm/test/Transforms/InstCombine/minmax-intrinsics.ll

  Log Message:
  -----------
  [InstCombine] add test with multiple uses of min/max negated operand; NFC


  Commit: 84cdccc9dc68ce11b8eb9a0cbb4333b7f3cb1c1e
      https://github.com/llvm/llvm-project/commit/84cdccc9dc68ce11b8eb9a0cbb4333b7f3cb1c1e
  Author: Sanjay Patel <spatel at rotateright.com>
  Date:   2021-04-09 (Fri, 09 Apr 2021)

  Changed paths:
    M llvm/lib/Transforms/InstCombine/InstCombineCalls.cpp
    M llvm/test/Transforms/InstCombine/minmax-intrinsics.ll

  Log Message:
  -----------
  [InstCombine] try to eliminate an instruction in min/max -> abs fold

As suggested in the review thread for 5094e12 and seen in the
motivating example from https://llvm.org/PR49885, it's not
clear if we have a way to create the optimal code without
this heuristic.


Compare: https://github.com/llvm/llvm-project/compare/5d7cb79416ad...84cdccc9dc68