2010-12-06 03:51:05 +08:00
|
|
|
//===-- PHIEliminationUtils.cpp - Helper functions for PHI elimination ----===//
|
|
|
|
//
|
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
|
2010-12-06 03:51:05 +08:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#include "PHIEliminationUtils.h"
|
2012-12-04 00:50:05 +08:00
|
|
|
#include "llvm/ADT/SmallPtrSet.h"
|
2010-12-06 03:51:05 +08:00
|
|
|
#include "llvm/CodeGen/MachineFunction.h"
|
|
|
|
#include "llvm/CodeGen/MachineRegisterInfo.h"
|
2020-09-03 23:47:21 +08:00
|
|
|
|
2010-12-06 03:51:05 +08:00
|
|
|
using namespace llvm;
|
|
|
|
|
|
|
|
// findCopyInsertPoint - Find a safe place in MBB to insert a copy from SrcReg
|
|
|
|
// when following the CFG edge to SuccMBB. This needs to be after any def of
|
|
|
|
// SrcReg, but before any subsequent point where control flow might jump out of
|
|
|
|
// the basic block.
|
|
|
|
MachineBasicBlock::iterator
|
|
|
|
llvm::findPHICopyInsertPoint(MachineBasicBlock* MBB, MachineBasicBlock* SuccMBB,
|
|
|
|
unsigned SrcReg) {
|
|
|
|
// Handle the trivial case trivially.
|
|
|
|
if (MBB->empty())
|
|
|
|
return MBB->begin();
|
|
|
|
|
|
|
|
// Usually, we just want to insert the copy before the first terminator
|
|
|
|
// instruction. However, for the edge going to a landing pad, we must insert
|
2020-05-16 11:43:30 +08:00
|
|
|
// the copy before the call/invoke instruction. Similarly for an INLINEASM_BR
|
PR47468: Fix findPHICopyInsertPoint, so that copies aren't incorrectly inserted after an INLINEASM_BR.
findPHICopyInsertPoint special cases placement in a block with a
callbr or invoke in it. In that case, we must ensure that the copy is
placed before the INLINEASM_BR or call instruction, if the register is
defined prior to that instruction, because it may jump out of the
block.
Previously, the code placed it immediately after the last def _or
use_. This is wrong, if the use is the instruction which may jump. We
could correctly place it immediately after the last def (ignoring
uses), but that is non-optimal for register pressure.
Instead, place the copy after the last def, or before the
call/inlineasm_br, whichever is later.
Differential Revision: https://reviews.llvm.org/D87865
2020-09-18 06:10:19 +08:00
|
|
|
// going to an indirect target. This is similar to SplitKit.cpp's
|
|
|
|
// computeLastInsertPoint, and similarly assumes that there cannot be multiple
|
|
|
|
// instructions that are Calls with EHPad successors or INLINEASM_BR in a
|
|
|
|
// block.
|
|
|
|
bool EHPadSuccessor = SuccMBB->isEHPad();
|
|
|
|
if (!EHPadSuccessor && !SuccMBB->isInlineAsmBrIndirectTarget())
|
2010-12-06 03:51:05 +08:00
|
|
|
return MBB->getFirstTerminator();
|
|
|
|
|
PR47468: Fix findPHICopyInsertPoint, so that copies aren't incorrectly inserted after an INLINEASM_BR.
findPHICopyInsertPoint special cases placement in a block with a
callbr or invoke in it. In that case, we must ensure that the copy is
placed before the INLINEASM_BR or call instruction, if the register is
defined prior to that instruction, because it may jump out of the
block.
Previously, the code placed it immediately after the last def _or
use_. This is wrong, if the use is the instruction which may jump. We
could correctly place it immediately after the last def (ignoring
uses), but that is non-optimal for register pressure.
Instead, place the copy after the last def, or before the
call/inlineasm_br, whichever is later.
Differential Revision: https://reviews.llvm.org/D87865
2020-09-18 06:10:19 +08:00
|
|
|
// Discover any defs in this basic block.
|
|
|
|
SmallPtrSet<MachineInstr *, 8> DefsInMBB;
|
2010-12-06 03:51:05 +08:00
|
|
|
MachineRegisterInfo& MRI = MBB->getParent()->getRegInfo();
|
PR47468: Fix findPHICopyInsertPoint, so that copies aren't incorrectly inserted after an INLINEASM_BR.
findPHICopyInsertPoint special cases placement in a block with a
callbr or invoke in it. In that case, we must ensure that the copy is
placed before the INLINEASM_BR or call instruction, if the register is
defined prior to that instruction, because it may jump out of the
block.
Previously, the code placed it immediately after the last def _or
use_. This is wrong, if the use is the instruction which may jump. We
could correctly place it immediately after the last def (ignoring
uses), but that is non-optimal for register pressure.
Instead, place the copy after the last def, or before the
call/inlineasm_br, whichever is later.
Differential Revision: https://reviews.llvm.org/D87865
2020-09-18 06:10:19 +08:00
|
|
|
for (MachineInstr &RI : MRI.def_instructions(SrcReg))
|
2014-03-18 03:36:09 +08:00
|
|
|
if (RI.getParent() == MBB)
|
PR47468: Fix findPHICopyInsertPoint, so that copies aren't incorrectly inserted after an INLINEASM_BR.
findPHICopyInsertPoint special cases placement in a block with a
callbr or invoke in it. In that case, we must ensure that the copy is
placed before the INLINEASM_BR or call instruction, if the register is
defined prior to that instruction, because it may jump out of the
block.
Previously, the code placed it immediately after the last def _or
use_. This is wrong, if the use is the instruction which may jump. We
could correctly place it immediately after the last def (ignoring
uses), but that is non-optimal for register pressure.
Instead, place the copy after the last def, or before the
call/inlineasm_br, whichever is later.
Differential Revision: https://reviews.llvm.org/D87865
2020-09-18 06:10:19 +08:00
|
|
|
DefsInMBB.insert(&RI);
|
2010-12-06 03:51:05 +08:00
|
|
|
|
PR47468: Fix findPHICopyInsertPoint, so that copies aren't incorrectly inserted after an INLINEASM_BR.
findPHICopyInsertPoint special cases placement in a block with a
callbr or invoke in it. In that case, we must ensure that the copy is
placed before the INLINEASM_BR or call instruction, if the register is
defined prior to that instruction, because it may jump out of the
block.
Previously, the code placed it immediately after the last def _or
use_. This is wrong, if the use is the instruction which may jump. We
could correctly place it immediately after the last def (ignoring
uses), but that is non-optimal for register pressure.
Instead, place the copy after the last def, or before the
call/inlineasm_br, whichever is later.
Differential Revision: https://reviews.llvm.org/D87865
2020-09-18 06:10:19 +08:00
|
|
|
MachineBasicBlock::iterator InsertPoint = MBB->begin();
|
|
|
|
// Insert the copy at the _latest_ point of:
|
|
|
|
// 1. Immediately AFTER the last def
|
|
|
|
// 2. Immediately BEFORE a call/inlineasm_br.
|
|
|
|
for (auto I = MBB->rbegin(), E = MBB->rend(); I != E; ++I) {
|
|
|
|
if (DefsInMBB.contains(&*I)) {
|
|
|
|
InsertPoint = std::next(I.getReverse());
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
if ((EHPadSuccessor && I->isCall()) ||
|
|
|
|
I->getOpcode() == TargetOpcode::INLINEASM_BR) {
|
|
|
|
InsertPoint = I.getReverse();
|
|
|
|
break;
|
|
|
|
}
|
2010-12-06 03:51:05 +08:00
|
|
|
}
|
|
|
|
|
2016-09-16 22:07:29 +08:00
|
|
|
// Make sure the copy goes after any phi nodes but before
|
|
|
|
// any debug nodes.
|
2010-12-06 03:51:05 +08:00
|
|
|
return MBB->SkipPHIsAndLabels(InsertPoint);
|
|
|
|
}
|