[all-commits] [llvm/llvm-project] 8b9f2b: [Metarenamer] Distinguish instructions by opcodes

[Max Kazantsev via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 8b9f2b6244d2ae8a3d469cff58bbb3dfa5e04575
      https://github.com/llvm/llvm-project/commit/8b9f2b6244d2ae8a3d469cff58bbb3dfa5e04575
  Author: Max Kazantsev <mkazantsev at azul.com>
  Date:   2023-03-16 (Thu, 16 Mar 2023)

  Changed paths:
    M llvm/lib/Transforms/Utils/MetaRenamer.cpp
    A llvm/test/Transforms/MetaRenamer/opcodes.ll

  Log Message:
  -----------
  [Metarenamer] Distinguish instructions by opcodes

This should improve readability of metarenamed code.

Differential Revision: https://reviews.llvm.org/D145896
Reviewed By: nikic


  Commit: 3b1951aceb8c58acd3d5c5ba2d042ad3d03c13c4
      https://github.com/llvm/llvm-project/commit/3b1951aceb8c58acd3d5c5ba2d042ad3d03c13c4
  Author: Max Kazantsev <mkazantsev at azul.com>
  Date:   2023-03-16 (Thu, 16 Mar 2023)

  Changed paths:
    A llvm/test/Transforms/GuardWidening/two_forms_behavior_consistency.ll

  Log Message:
  -----------
  [Test] Add test showing difference in behavior of Guard Widening depending on form

Guards can be represented differently (as intrinsic calls and as explicit branches),
and the expectation is that Guard Widening should do the same things for them, no
matter what form it was suggested. Currently it seems to be not so.

We also don't want LICM to prevent guard widening.


Compare: https://github.com/llvm/llvm-project/compare/61d2f3a71e61...3b1951aceb8c