forked from OSchip/llvm-project
Reprioritize tests for tail duplication to be aggressive about indirect
branches even when optimizing for code size. Unless we find evidence to the contrary in the future, the special treatment for indirect branches does not have a significant effect on code size, and performance still matters with -Os. llvm-svn: 90147
This commit is contained in:
parent
89b660c774
commit
598f8ff9e5
|
@ -116,14 +116,14 @@ bool TailDuplicatePass::TailDuplicate(MachineBasicBlock *TailBB,
|
|||
// duplicate only one, because one branch instruction can be eliminated to
|
||||
// compensate for the duplication.
|
||||
unsigned MaxDuplicateCount;
|
||||
if (MF.getFunction()->hasFnAttr(Attribute::OptimizeForSize))
|
||||
MaxDuplicateCount = 1;
|
||||
else if (!TailBB->empty() && TailBB->back().getDesc().isIndirectBranch())
|
||||
if (!TailBB->empty() && TailBB->back().getDesc().isIndirectBranch())
|
||||
// If the target has hardware branch prediction that can handle indirect
|
||||
// branches, duplicating them can often make them predictable when there
|
||||
// are common paths through the code. The limit needs to be high enough
|
||||
// to allow undoing the effects of tail merging.
|
||||
MaxDuplicateCount = 20;
|
||||
else if (MF.getFunction()->hasFnAttr(Attribute::OptimizeForSize))
|
||||
MaxDuplicateCount = 1;
|
||||
else
|
||||
MaxDuplicateCount = TailDuplicateSize;
|
||||
|
||||
|
|
Loading…
Reference in New Issue