2017-06-07 06:22:41 +08:00
|
|
|
//===- TargetFrameLoweringImpl.cpp - Implement target frame interface ------==//
|
2005-04-22 06:55:34 +08:00
|
|
|
//
|
2019-01-19 16:50:56 +08:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2005-04-22 06:55:34 +08:00
|
|
|
//
|
2004-03-12 07:52:43 +08:00
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// Implements the layout of a stack frame on the target machine.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2015-07-15 01:17:13 +08:00
|
|
|
#include "llvm/ADT/BitVector.h"
|
2010-11-21 00:14:57 +08:00
|
|
|
#include "llvm/CodeGen/MachineFrameInfo.h"
|
|
|
|
#include "llvm/CodeGen/MachineFunction.h"
|
2015-07-15 01:17:13 +08:00
|
|
|
#include "llvm/CodeGen/MachineRegisterInfo.h"
|
2022-03-15 17:54:19 +08:00
|
|
|
#include "llvm/CodeGen/TargetFrameLowering.h"
|
2017-11-17 09:07:10 +08:00
|
|
|
#include "llvm/CodeGen/TargetSubtargetInfo.h"
|
2017-06-07 06:22:41 +08:00
|
|
|
#include "llvm/IR/Attributes.h"
|
HHVM calling conventions.
HHVM calling convention, hhvmcc, is used by HHVM JIT for
functions in translated cache. We currently support LLVM back end to
generate code for X86-64 and may support other architectures in the
future.
In HHVM calling convention any GP register could be used to pass and
return values, with the exception of R12 which is reserved for
thread-local area and is callee-saved. Other than R12, we always
pass RBX and RBP as args, which are our virtual machine's stack pointer
and frame pointer respectively.
When we enter translation cache via hhvmcc function, we expect
the stack to be aligned at 16 bytes, i.e. skewed by 8 bytes as opposed
to standard ABI alignment. This affects stack object alignment and stack
adjustments for function calls.
One extra calling convention, hhvm_ccc, is used to call C++ helpers from
HHVM's translation cache. It is almost identical to standard C calling
convention with an exception of first argument which is passed in RBP
(before we use RDI, RSI, etc.)
Differential Revision: http://reviews.llvm.org/D12681
llvm-svn: 248832
2015-09-30 06:09:16 +08:00
|
|
|
#include "llvm/IR/CallingConv.h"
|
2015-05-23 09:14:08 +08:00
|
|
|
#include "llvm/IR/Function.h"
|
2020-04-13 14:43:06 +08:00
|
|
|
#include "llvm/IR/InstrTypes.h"
|
[CodeGen] Async unwind - add a pass to fix CFI information
This pass inserts the necessary CFI instructions to compensate for the
inconsistency of the call-frame information caused by linear (non-CGA
aware) nature of the unwind tables.
Unlike the `CFIInstrInserer` pass, this one almost always emits only
`.cfi_remember_state`/`.cfi_restore_state`, which results in smaller
unwind tables and also transparently handles custom unwind info
extensions like CFA offset adjustement and save locations of SVE
registers.
This pass takes advantage of the constraints taht LLVM imposes on the
placement of save/restore points (cf. `ShrinkWrap.cpp`):
* there is a single basic block, containing the function prologue
* possibly multiple epilogue blocks, where each epilogue block is
complete and self-contained, i.e. CSR restore instructions (and the
corresponding CFI instructions are not split across two or more
blocks.
* prologue and epilogue blocks are outside of any loops
Thus, during execution, at the beginning and at the end of each basic
block the function can be in one of two states:
- "has a call frame", if the function has executed the prologue, or
has not executed any epilogue
- "does not have a call frame", if the function has not executed the
prologue, or has executed an epilogue
These properties can be computed for each basic block by a single RPO
traversal.
From the point of view of the unwind tables, the "has/does not have
call frame" state at beginning of each block is determined by the
state at the end of the previous block, in layout order.
Where these states differ, we insert compensating CFI instructions,
which come in two flavours:
- CFI instructions, which reset the unwind table state to the
initial one. This is done by a target specific hook and is
expected to be trivial to implement, for example it could be:
```
.cfi_def_cfa <sp>, 0
.cfi_same_value <rN>
.cfi_same_value <rN-1>
...
```
where `<rN>` are the callee-saved registers.
- CFI instructions, which reset the unwind table state to the one
created by the function prologue. These are the sequence:
```
.cfi_restore_state
.cfi_remember_state
```
In this case we also insert a `.cfi_remember_state` after the
last CFI instruction in the function prologue.
Reviewed By: MaskRay, danielkiss, chill
Differential Revision: https://reviews.llvm.org/D114545
2022-04-11 19:08:26 +08:00
|
|
|
#include "llvm/MC/MCAsmInfo.h"
|
|
|
|
#include "llvm/MC/MCRegisterInfo.h"
|
2017-06-07 06:22:41 +08:00
|
|
|
#include "llvm/Support/Compiler.h"
|
|
|
|
#include "llvm/Target/TargetMachine.h"
|
|
|
|
#include "llvm/Target/TargetOptions.h"
|
|
|
|
|
2004-03-12 07:52:43 +08:00
|
|
|
using namespace llvm;
|
|
|
|
|
2017-06-07 06:22:41 +08:00
|
|
|
TargetFrameLowering::~TargetFrameLowering() = default;
|
2010-11-19 07:25:52 +08:00
|
|
|
|
2018-04-07 18:57:03 +08:00
|
|
|
bool TargetFrameLowering::enableCalleeSaveSkip(const MachineFunction &MF) const {
|
|
|
|
assert(MF.getFunction().hasFnAttribute(Attribute::NoReturn) &&
|
|
|
|
MF.getFunction().hasFnAttribute(Attribute::NoUnwind) &&
|
|
|
|
!MF.getFunction().hasFnAttribute(Attribute::UWTable));
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
[CodeGen] Async unwind - add a pass to fix CFI information
This pass inserts the necessary CFI instructions to compensate for the
inconsistency of the call-frame information caused by linear (non-CGA
aware) nature of the unwind tables.
Unlike the `CFIInstrInserer` pass, this one almost always emits only
`.cfi_remember_state`/`.cfi_restore_state`, which results in smaller
unwind tables and also transparently handles custom unwind info
extensions like CFA offset adjustement and save locations of SVE
registers.
This pass takes advantage of the constraints taht LLVM imposes on the
placement of save/restore points (cf. `ShrinkWrap.cpp`):
* there is a single basic block, containing the function prologue
* possibly multiple epilogue blocks, where each epilogue block is
complete and self-contained, i.e. CSR restore instructions (and the
corresponding CFI instructions are not split across two or more
blocks.
* prologue and epilogue blocks are outside of any loops
Thus, during execution, at the beginning and at the end of each basic
block the function can be in one of two states:
- "has a call frame", if the function has executed the prologue, or
has not executed any epilogue
- "does not have a call frame", if the function has not executed the
prologue, or has executed an epilogue
These properties can be computed for each basic block by a single RPO
traversal.
From the point of view of the unwind tables, the "has/does not have
call frame" state at beginning of each block is determined by the
state at the end of the previous block, in layout order.
Where these states differ, we insert compensating CFI instructions,
which come in two flavours:
- CFI instructions, which reset the unwind table state to the
initial one. This is done by a target specific hook and is
expected to be trivial to implement, for example it could be:
```
.cfi_def_cfa <sp>, 0
.cfi_same_value <rN>
.cfi_same_value <rN-1>
...
```
where `<rN>` are the callee-saved registers.
- CFI instructions, which reset the unwind table state to the one
created by the function prologue. These are the sequence:
```
.cfi_restore_state
.cfi_remember_state
```
In this case we also insert a `.cfi_remember_state` after the
last CFI instruction in the function prologue.
Reviewed By: MaskRay, danielkiss, chill
Differential Revision: https://reviews.llvm.org/D114545
2022-04-11 19:08:26 +08:00
|
|
|
bool TargetFrameLowering::enableCFIFixup(MachineFunction &MF) const {
|
|
|
|
return MF.needsFrameMoves() &&
|
|
|
|
!MF.getTarget().getMCAsmInfo()->usesWindowsCFI();
|
|
|
|
}
|
|
|
|
|
2015-08-15 10:32:35 +08:00
|
|
|
/// Returns the displacement from the frame register to the stack
|
|
|
|
/// frame of the specified index, along with the frame register used
|
|
|
|
/// (in output arg FrameReg). This is the default implementation which
|
|
|
|
/// is overridden for some targets.
|
2020-11-04 16:56:54 +08:00
|
|
|
StackOffset
|
|
|
|
TargetFrameLowering::getFrameIndexReference(const MachineFunction &MF, int FI,
|
|
|
|
Register &FrameReg) const {
|
2016-07-29 02:40:00 +08:00
|
|
|
const MachineFrameInfo &MFI = MF.getFrameInfo();
|
2014-08-05 10:39:49 +08:00
|
|
|
const TargetRegisterInfo *RI = MF.getSubtarget().getRegisterInfo();
|
2010-11-20 23:59:32 +08:00
|
|
|
|
|
|
|
// By default, assume all frame indices are referenced via whatever
|
|
|
|
// getFrameRegister() says. The target can override this if it's doing
|
|
|
|
// something different.
|
|
|
|
FrameReg = RI->getFrameRegister(MF);
|
2015-08-15 10:32:35 +08:00
|
|
|
|
2020-11-04 16:56:54 +08:00
|
|
|
return StackOffset::getFixed(MFI.getObjectOffset(FI) + MFI.getStackSize() -
|
|
|
|
getOffsetOfLocalArea() +
|
|
|
|
MFI.getOffsetAdjustment());
|
2010-11-20 23:59:32 +08:00
|
|
|
}
|
2015-02-02 00:56:04 +08:00
|
|
|
|
|
|
|
bool TargetFrameLowering::needsFrameIndexResolution(
|
|
|
|
const MachineFunction &MF) const {
|
2016-07-29 02:40:00 +08:00
|
|
|
return MF.getFrameInfo().hasStackObjects();
|
2015-02-02 00:56:04 +08:00
|
|
|
}
|
2015-07-15 01:17:13 +08:00
|
|
|
|
2019-10-29 20:49:34 +08:00
|
|
|
void TargetFrameLowering::getCalleeSaves(const MachineFunction &MF,
|
|
|
|
BitVector &CalleeSaves) const {
|
|
|
|
const TargetRegisterInfo &TRI = *MF.getSubtarget().getRegisterInfo();
|
|
|
|
CalleeSaves.resize(TRI.getNumRegs());
|
|
|
|
|
|
|
|
const MachineFrameInfo &MFI = MF.getFrameInfo();
|
|
|
|
if (!MFI.isCalleeSavedInfoValid())
|
|
|
|
return;
|
|
|
|
|
|
|
|
for (const CalleeSavedInfo &Info : MFI.getCalleeSavedInfo())
|
|
|
|
CalleeSaves.set(Info.getReg());
|
|
|
|
}
|
|
|
|
|
2015-07-15 01:17:13 +08:00
|
|
|
void TargetFrameLowering::determineCalleeSaves(MachineFunction &MF,
|
|
|
|
BitVector &SavedRegs,
|
|
|
|
RegScavenger *RS) const {
|
|
|
|
const TargetRegisterInfo &TRI = *MF.getSubtarget().getRegisterInfo();
|
|
|
|
|
2016-04-08 20:04:32 +08:00
|
|
|
// Resize before the early returns. Some backends expect that
|
|
|
|
// SavedRegs.size() == TRI.getNumRegs() after this call even if there are no
|
|
|
|
// saved registers.
|
|
|
|
SavedRegs.resize(TRI.getNumRegs());
|
|
|
|
|
2016-07-14 07:39:34 +08:00
|
|
|
// When interprocedural register allocation is enabled caller saved registers
|
|
|
|
// are preferred over callee saved registers.
|
2019-08-02 18:23:17 +08:00
|
|
|
if (MF.getTarget().Options.EnableIPRA &&
|
|
|
|
isSafeForNoCSROpt(MF.getFunction()) &&
|
|
|
|
isProfitableForNoCSROpt(MF.getFunction()))
|
2016-07-14 07:39:34 +08:00
|
|
|
return;
|
|
|
|
|
|
|
|
// Get the callee saved register list...
|
2017-03-14 17:09:26 +08:00
|
|
|
const MCPhysReg *CSRegs = MF.getRegInfo().getCalleeSavedRegs();
|
2016-07-14 07:39:34 +08:00
|
|
|
|
2015-07-15 01:17:13 +08:00
|
|
|
// Early exit if there are no callee saved registers.
|
|
|
|
if (!CSRegs || CSRegs[0] == 0)
|
|
|
|
return;
|
|
|
|
|
|
|
|
// In Naked functions we aren't going to save any registers.
|
2017-12-16 06:22:58 +08:00
|
|
|
if (MF.getFunction().hasFnAttribute(Attribute::Naked))
|
2015-07-15 01:17:13 +08:00
|
|
|
return;
|
|
|
|
|
2018-04-07 18:57:03 +08:00
|
|
|
// Noreturn+nounwind functions never restore CSR, so no saves are needed.
|
|
|
|
// Purely noreturn functions may still return through throws, so those must
|
|
|
|
// save CSR for caller exception handlers.
|
|
|
|
//
|
|
|
|
// If the function uses longjmp to break out of its current path of
|
|
|
|
// execution we do not need the CSR spills either: setjmp stores all CSRs
|
|
|
|
// it was called with into the jmp_buf, which longjmp then restores.
|
|
|
|
if (MF.getFunction().hasFnAttribute(Attribute::NoReturn) &&
|
|
|
|
MF.getFunction().hasFnAttribute(Attribute::NoUnwind) &&
|
|
|
|
!MF.getFunction().hasFnAttribute(Attribute::UWTable) &&
|
|
|
|
enableCalleeSaveSkip(MF))
|
|
|
|
return;
|
|
|
|
|
2015-07-15 01:17:13 +08:00
|
|
|
// Functions which call __builtin_unwind_init get all their registers saved.
|
2016-12-02 03:32:15 +08:00
|
|
|
bool CallsUnwindInit = MF.callsUnwindInit();
|
2015-07-15 01:17:13 +08:00
|
|
|
const MachineRegisterInfo &MRI = MF.getRegInfo();
|
|
|
|
for (unsigned i = 0; CSRegs[i]; ++i) {
|
|
|
|
unsigned Reg = CSRegs[i];
|
|
|
|
if (CallsUnwindInit || MRI.isPhysRegModified(Reg))
|
|
|
|
SavedRegs.set(Reg);
|
|
|
|
}
|
|
|
|
}
|
HHVM calling conventions.
HHVM calling convention, hhvmcc, is used by HHVM JIT for
functions in translated cache. We currently support LLVM back end to
generate code for X86-64 and may support other architectures in the
future.
In HHVM calling convention any GP register could be used to pass and
return values, with the exception of R12 which is reserved for
thread-local area and is callee-saved. Other than R12, we always
pass RBX and RBP as args, which are our virtual machine's stack pointer
and frame pointer respectively.
When we enter translation cache via hhvmcc function, we expect
the stack to be aligned at 16 bytes, i.e. skewed by 8 bytes as opposed
to standard ABI alignment. This affects stack object alignment and stack
adjustments for function calls.
One extra calling convention, hhvm_ccc, is used to call C++ helpers from
HHVM's translation cache. It is almost identical to standard C calling
convention with an exception of first argument which is passed in RBP
(before we use RDI, RSI, etc.)
Differential Revision: http://reviews.llvm.org/D12681
llvm-svn: 248832
2015-09-30 06:09:16 +08:00
|
|
|
|
|
|
|
unsigned TargetFrameLowering::getStackAlignmentSkew(
|
|
|
|
const MachineFunction &MF) const {
|
|
|
|
// When HHVM function is called, the stack is skewed as the return address
|
|
|
|
// is removed from the stack before we enter the function.
|
2017-12-16 06:22:58 +08:00
|
|
|
if (LLVM_UNLIKELY(MF.getFunction().getCallingConv() == CallingConv::HHVM))
|
2018-03-14 08:36:23 +08:00
|
|
|
return MF.getTarget().getAllocaPointerSize();
|
HHVM calling conventions.
HHVM calling convention, hhvmcc, is used by HHVM JIT for
functions in translated cache. We currently support LLVM back end to
generate code for X86-64 and may support other architectures in the
future.
In HHVM calling convention any GP register could be used to pass and
return values, with the exception of R12 which is reserved for
thread-local area and is callee-saved. Other than R12, we always
pass RBX and RBP as args, which are our virtual machine's stack pointer
and frame pointer respectively.
When we enter translation cache via hhvmcc function, we expect
the stack to be aligned at 16 bytes, i.e. skewed by 8 bytes as opposed
to standard ABI alignment. This affects stack object alignment and stack
adjustments for function calls.
One extra calling convention, hhvm_ccc, is used to call C++ helpers from
HHVM's translation cache. It is almost identical to standard C calling
convention with an exception of first argument which is passed in RBP
(before we use RDI, RSI, etc.)
Differential Revision: http://reviews.llvm.org/D12681
llvm-svn: 248832
2015-09-30 06:09:16 +08:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2018-04-24 18:32:08 +08:00
|
|
|
|
2021-11-04 09:01:53 +08:00
|
|
|
bool TargetFrameLowering::allocateScavengingFrameIndexesNearIncomingSP(
|
|
|
|
const MachineFunction &MF) const {
|
|
|
|
if (!hasFP(MF))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
const TargetRegisterInfo *RegInfo = MF.getSubtarget().getRegisterInfo();
|
|
|
|
return RegInfo->useFPForScavengingIndex(MF) &&
|
|
|
|
!RegInfo->hasStackRealignment(MF);
|
|
|
|
}
|
|
|
|
|
2019-10-19 08:22:07 +08:00
|
|
|
bool TargetFrameLowering::isSafeForNoCSROpt(const Function &F) {
|
|
|
|
if (!F.hasLocalLinkage() || F.hasAddressTaken() ||
|
|
|
|
!F.hasFnAttribute(Attribute::NoRecurse))
|
|
|
|
return false;
|
|
|
|
// Function should not be optimized as tail call.
|
|
|
|
for (const User *U : F.users())
|
2020-04-13 14:43:06 +08:00
|
|
|
if (auto *CB = dyn_cast<CallBase>(U))
|
|
|
|
if (CB->isTailCall())
|
2019-10-19 08:22:07 +08:00
|
|
|
return false;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2018-04-24 18:32:08 +08:00
|
|
|
int TargetFrameLowering::getInitialCFAOffset(const MachineFunction &MF) const {
|
|
|
|
llvm_unreachable("getInitialCFAOffset() not implemented!");
|
|
|
|
}
|
|
|
|
|
2020-04-08 04:33:58 +08:00
|
|
|
Register
|
|
|
|
TargetFrameLowering::getInitialCFARegister(const MachineFunction &MF) const {
|
2018-04-24 18:32:08 +08:00
|
|
|
llvm_unreachable("getInitialCFARegister() not implemented!");
|
2019-10-19 08:22:07 +08:00
|
|
|
}
|
2019-12-19 06:50:19 +08:00
|
|
|
|
|
|
|
TargetFrameLowering::DwarfFrameBase
|
|
|
|
TargetFrameLowering::getDwarfFrameBase(const MachineFunction &MF) const {
|
|
|
|
const TargetRegisterInfo *RI = MF.getSubtarget().getRegisterInfo();
|
|
|
|
return DwarfFrameBase{DwarfFrameBase::Register, {RI->getFrameRegister(MF)}};
|
|
|
|
}
|