mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2025-01-31 20:51:52 +01:00
[MachineBlockPlacement] Let the target optimize the branches at the end.
After the layout of the basic blocks is set, the target may be able to get rid of unconditional branches to fallthrough blocks that the generic code does not catch. This happens any time TargetInstrInfo::AnalyzeBranch is not able to analyze all the branches involved in the terminators sequence, while still understanding a few of them. In such situation, AnalyzeBranch can directly modify the branches if it has been instructed to do so. This patch takes advantage of that. llvm-svn: 268328
This commit is contained in:
parent
6b53c89899
commit
cf0d20f78c
@ -1358,6 +1358,19 @@ void MachineBlockPlacement::buildCFGChains(MachineFunction &F) {
|
||||
MachineBasicBlock *TBB = nullptr, *FBB = nullptr; // For AnalyzeBranch.
|
||||
if (!TII->AnalyzeBranch(F.back(), TBB, FBB, Cond))
|
||||
F.back().updateTerminator();
|
||||
|
||||
// Now that all the basic blocks in the chain have the proper layout,
|
||||
// make a final call to AnalyzeBranch with AllowModify set.
|
||||
// Indeed, the target may be able to optimize the branches in a way we
|
||||
// cannot because all branches may not be analyzable.
|
||||
// E.g., the target may be able to remove an unconditional branch to
|
||||
// a fallthrough when it occurs after predicated terminators.
|
||||
for (MachineBasicBlock *ChainBB : FunctionChain) {
|
||||
Cond.clear();
|
||||
TBB = nullptr;
|
||||
FBB = nullptr; // For AnalyzeBranch.
|
||||
(void)TII->AnalyzeBranch(*ChainBB, TBB, FBB, Cond, /*AllowModify*/ true);
|
||||
}
|
||||
}
|
||||
|
||||
void MachineBlockPlacement::alignBlocks(MachineFunction &F) {
|
||||
|
@ -218,10 +218,10 @@ define i32 @imp_null_check_via_mem_comparision(i32* %x, i32 %val) {
|
||||
; OBJDUMP-NEXT: Version: 0x1
|
||||
; OBJDUMP-NEXT: NumFunctions: 5
|
||||
; OBJDUMP-NEXT: FunctionAddress: 0x000000, NumFaultingPCs: 1
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 5
|
||||
; OBJDUMP-NEXT: FunctionAddress: 0x000000, NumFaultingPCs: 1
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 7
|
||||
; OBJDUMP-NEXT: FunctionAddress: 0x000000, NumFaultingPCs: 1
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 9
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 7
|
||||
; OBJDUMP-NEXT: FunctionAddress: 0x000000, NumFaultingPCs: 1
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 9
|
||||
; OBJDUMP-NEXT: FunctionAddress: 0x000000, NumFaultingPCs: 1
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 5
|
||||
; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 3
|
||||
|
Loading…
x
Reference in New Issue
Block a user