maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Transforms/SimplifyCFG/PhiEliminate2.ll

35 lines
1.0 KiB
LLVM
Raw Normal View History

update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
; RUN: opt < %s -simplifycfg -S | FileCheck %s
Simplify cfg now eliminates all of the branches in this testcase llvm-svn: 12803
2004-04-10 07:50:29 +08:00
allow branch weight metadata on select instructions (PR26636) As noted in: https://llvm.org/bugs/show_bug.cgi?id=26636 This doesn't accomplish anything on its own. It's the first step towards preserving and using branch weights with selects. The next step would be to make sure we're propagating the info in all of the other places where we create selects (SimplifyCFG, InstCombine, etc). I don't think there's an easy fix to make this happen; we have to look at each transform individually to determine how to correctly propagate the weights. Along with that step, we need to then use the weights when making subsequent transform decisions such as discussed in http://reviews.llvm.org/D16836. The inliner test is independent but closely related. It verifies that metadata is preserved when both branches and selects are cloned. Differential Revision: http://reviews.llvm.org/D18133 llvm-svn: 263482
2016-03-15 04:18:59 +08:00
; Use a select to make this a single BB.
; Also, make sure the profile metadata is propagated to the select (PR26636).
update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
define i32 @FoldTwoEntryPHINode(i1 %C, i32 %V1, i32 %V2, i16 %V3) {
Simplify cfg now eliminates all of the branches in this testcase llvm-svn: 12803
2004-04-10 07:50:29 +08:00
entry:
propagate 'unpredictable' metadata on select instructions This is similar to D18133 where we allowed profile weights on select instructions. This extends that change to also allow the 'unpredictable' attribute of branches to apply to selects. A test to check that 'unpredictable' metadata is preserved when cloning instructions was checked in at: http://reviews.llvm.org/rL263648 Differential Revision: http://reviews.llvm.org/D18220 llvm-svn: 263716
2016-03-17 23:30:52 +08:00
br i1 %C, label %then, label %else, !prof !0, !unpredictable !1
update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
then:
%V4 = or i32 %V2, %V1
Simplify cfg now eliminates all of the branches in this testcase llvm-svn: 12803
2004-04-10 07:50:29 +08:00
br label %Cont
update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
else:
%V5 = sext i16 %V3 to i32
SimplifyCFG: Add Trunc, ZExt and SExt to the list of cheap instructions for phi node folding llvm-svn: 130526
2011-04-30 02:47:25 +08:00
br label %Cont
update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
Cont:
%V6 = phi i32 [ %V5, %else ], [ %V4, %then ]
call i32 @FoldTwoEntryPHINode( i1 false, i32 0, i32 0, i16 0 )
Upgrade tests to not use llvm-upgrade. llvm-svn: 48483
2008-03-18 11:45:45 +08:00
ret i32 %V1
update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
; CHECK-LABEL: @FoldTwoEntryPHINode(
; CHECK-NEXT: entry:
; CHECK-NEXT: %V5 = sext i16 %V3 to i32
; CHECK-NEXT: %V4 = or i32 %V2, %V1
propagate 'unpredictable' metadata on select instructions This is similar to D18133 where we allowed profile weights on select instructions. This extends that change to also allow the 'unpredictable' attribute of branches to apply to selects. A test to check that 'unpredictable' metadata is preserved when cloning instructions was checked in at: http://reviews.llvm.org/rL263648 Differential Revision: http://reviews.llvm.org/D18220 llvm-svn: 263716
2016-03-17 23:30:52 +08:00
; CHECK-NEXT: %V6 = select i1 %C, i32 %V4, i32 %V5, !prof !0, !unpredictable !1
update test to use FileCheck llvm-svn: 263347
2016-03-13 05:09:26 +08:00
; CHECK-NEXT: %0 = call i32 @FoldTwoEntryPHINode(i1 false, i32 0, i32 0, i16 0)
; CHECK-NEXT: ret i32 %V1
Simplify cfg now eliminates all of the branches in this testcase llvm-svn: 12803
2004-04-10 07:50:29 +08:00
}
allow branch weight metadata on select instructions (PR26636) As noted in: https://llvm.org/bugs/show_bug.cgi?id=26636 This doesn't accomplish anything on its own. It's the first step towards preserving and using branch weights with selects. The next step would be to make sure we're propagating the info in all of the other places where we create selects (SimplifyCFG, InstCombine, etc). I don't think there's an easy fix to make this happen; we have to look at each transform individually to determine how to correctly propagate the weights. Along with that step, we need to then use the weights when making subsequent transform decisions such as discussed in http://reviews.llvm.org/D16836. The inliner test is independent but closely related. It verifies that metadata is preserved when both branches and selects are cloned. Differential Revision: http://reviews.llvm.org/D18133 llvm-svn: 263482
2016-03-15 04:18:59 +08:00
!0 = !{!"branch_weights", i32 3, i32 5}
propagate 'unpredictable' metadata on select instructions This is similar to D18133 where we allowed profile weights on select instructions. This extends that change to also allow the 'unpredictable' attribute of branches to apply to selects. A test to check that 'unpredictable' metadata is preserved when cloning instructions was checked in at: http://reviews.llvm.org/rL263648 Differential Revision: http://reviews.llvm.org/D18220 llvm-svn: 263716
2016-03-17 23:30:52 +08:00
!1 = !{}
allow branch weight metadata on select instructions (PR26636) As noted in: https://llvm.org/bugs/show_bug.cgi?id=26636 This doesn't accomplish anything on its own. It's the first step towards preserving and using branch weights with selects. The next step would be to make sure we're propagating the info in all of the other places where we create selects (SimplifyCFG, InstCombine, etc). I don't think there's an easy fix to make this happen; we have to look at each transform individually to determine how to correctly propagate the weights. Along with that step, we need to then use the weights when making subsequent transform decisions such as discussed in http://reviews.llvm.org/D16836. The inliner test is independent but closely related. It verifies that metadata is preserved when both branches and selects are cloned. Differential Revision: http://reviews.llvm.org/D18133 llvm-svn: 263482
2016-03-15 04:18:59 +08:00
; CHECK: !0 = !{!"branch_weights", i32 3, i32 5}
propagate 'unpredictable' metadata on select instructions This is similar to D18133 where we allowed profile weights on select instructions. This extends that change to also allow the 'unpredictable' attribute of branches to apply to selects. A test to check that 'unpredictable' metadata is preserved when cloning instructions was checked in at: http://reviews.llvm.org/rL263648 Differential Revision: http://reviews.llvm.org/D18220 llvm-svn: 263716
2016-03-17 23:30:52 +08:00
; CHECK: !1 = !{}
allow branch weight metadata on select instructions (PR26636) As noted in: https://llvm.org/bugs/show_bug.cgi?id=26636 This doesn't accomplish anything on its own. It's the first step towards preserving and using branch weights with selects. The next step would be to make sure we're propagating the info in all of the other places where we create selects (SimplifyCFG, InstCombine, etc). I don't think there's an easy fix to make this happen; we have to look at each transform individually to determine how to correctly propagate the weights. Along with that step, we need to then use the weights when making subsequent transform decisions such as discussed in http://reviews.llvm.org/D16836. The inliner test is independent but closely related. It verifies that metadata is preserved when both branches and selects are cloned. Differential Revision: http://reviews.llvm.org/D18133 llvm-svn: 263482
2016-03-15 04:18:59 +08:00