[all-commits] [llvm/llvm-project] a6a07a: [MachineOutliner] Don't outline functions starting...
Fangrui Song via All-commits
all-commits at lists.llvm.org
Mon Dec 13 13:24:44 PST 2021
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: a6a07a514b8a084feaa7f4f15d569698b9840d83
https://github.com/llvm/llvm-project/commit/a6a07a514b8a084feaa7f4f15d569698b9840d83
Author: Fangrui Song <i at maskray.me>
Date: 2021-12-13 (Mon, 13 Dec 2021)
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
More information about the All-commits
mailing list