[all-commits] [llvm/llvm-project] 0d4420: [MachineOutliner] Don't outline functions starting...

[Fangrui Song via All-commits]

  Branch: refs/heads/release/13.x
  Home:   https://github.com/llvm/llvm-project
  Commit: 0d44201451f03ba907cdb268ddddfc3fa38a0ebd
      https://github.com/llvm/llvm-project/commit/0d44201451f03ba907cdb268ddddfc3fa38a0ebd
  Author: Fangrui Song <i at maskray.me>
  Date:   2022-01-05 (Wed, 05 Jan 2022)

  Changed paths:
    M llvm/include/llvm/CodeGen/TargetInstrInfo.h
    M llvm/lib/CodeGen/TargetInstrInfo.cpp
    M llvm/lib/Target/AArch64/AArch64InstrInfo.cpp
    M llvm/lib/Target/RISCV/RISCVInstrInfo.cpp
    A llvm/test/CodeGen/AArch64/machine-outliner-patchable.ll
    A llvm/test/CodeGen/RISCV/machine-outliner-patchable.ll

  Log Message:
  -----------
  [MachineOutliner] Don't outline functions starting with PATCHABLE_FUNCTION_ENTER/FENTRL_CALL

MachineOutliner may outline a "patchable-function-entry" function whose body has
a TargetOpcode::PATCHABLE_FUNCTION_ENTER MachineInstr. This is incorrect because
the special code sequence must stay unchanged to be used at run-time.
Avoid outlining PATCHABLE_FUNCTION_ENTER. While here, avoid outlining FENTRY_CALL too
(which doesn't reproduce currently) to allow phase ordering flexibility.

Fixes #52635

Reviewed By: paquette

Differential Revision: https://reviews.llvm.org/D115614

(cherry picked from commit a6a07a514b8a084feaa7f4f15d569698b9840d83)