diff options
| author | Quentin Colombet <qcolombet@apple.com> | 2016-05-02 22:58:59 +0000 |
|---|---|---|
| committer | Quentin Colombet <qcolombet@apple.com> | 2016-05-02 22:58:59 +0000 |
| commit | 776e6de51626b01b6e4d062c243e48bcc9446884 (patch) | |
| tree | ee315b33525a5506702831b78fd6e1c2572561bd /llvm/test/CodeGen/X86/implicit-null-check.ll | |
| parent | 4e1d389ac5cf5048d2c4e90caa2de672d7445148 (diff) | |
| download | bcm5719-llvm-776e6de51626b01b6e4d062c243e48bcc9446884.tar.gz bcm5719-llvm-776e6de51626b01b6e4d062c243e48bcc9446884.zip | |
[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
Diffstat (limited to 'llvm/test/CodeGen/X86/implicit-null-check.ll')
| -rw-r--r-- | llvm/test/CodeGen/X86/implicit-null-check.ll | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/llvm/test/CodeGen/X86/implicit-null-check.ll b/llvm/test/CodeGen/X86/implicit-null-check.ll index 166408de529..b4c9b5834c8 100644 --- a/llvm/test/CodeGen/X86/implicit-null-check.ll +++ b/llvm/test/CodeGen/X86/implicit-null-check.ll @@ -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: 7 +; 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: 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: 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: 5 +; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 3 |
