Searched refs:LBB0_2 (Results 1 – 23 of 23) sorted by relevance
8 ; jnp LBB0_211 ; LBB0_2:17 ; jne LBB0_218 ; jp LBB0_220 ; LBB0_2:
27 ; CHECK: jne LBB0_229 ; CHECK: LBB0_2:
26 ; X32-NEXT: ja .LBB0_247 ; X64-NEXT: ja .LBB0_2
37 ; X32-Linux-NEXT: ja .LBB0_247 ; X64-Linux-NEXT: ja .LBB0_258 ; X32-Darwin-NEXT: ja LBB0_268 ; X64-Darwin-NEXT: ja LBB0_278 ; X32-MinGW-NEXT: ja LBB0_288 ; X64-MinGW-NEXT: ja .LBB0_298 ; X64-FreeBSD-NEXT: ja .LBB0_2
6 ; CHECK: jmp LBB0_2
18 ; CHECK: LBB0_2:
12 ; CHECK-NEXT: .LBB0_2:
7 ; CHECK: jne LBB0_2
19 je LBB0_225 LBB0_2: # %return label
18 .LBB0_2: // %lbl1 label39 .xword .LBB0_2
5 ; CHECK: .long LBB0_26 ; CHECK: LBB0_2:
30 ; ARM-linux-NEXT: blo .LBB0_250 ; ARM-android-NEXT: blo .LBB0_2
38 ; THUMB: LBB0_2
24 ; ARM-linux-NEXT: blo .LBB0_243 ; ARM-android-NEXT: blo .LBB0_2
23 ; ARM-linux-NEXT: blo .LBB0_2
40 jg .LBB0_247 .LBB0_2:57 into ``.LBB0_2``. This is possible since both, the size of the ``ret``
30 ; Thumb-linux-NEXT: blo .LBB0_250 ; Thumb-android-NEXT: blo .LBB0_2
22 ; Thumb-android-NEXT: blo .LBB0_242 ; Thumb-linux-NEXT: blo .LBB0_2
23 ; CHECK: LBB0_2
20 ; Thumb-android-NEXT: blo .LBB0_2
51 ; CHECK-NEXT: .short .LBB0_2
102 je LBB0_21156 je .LBB0_21161 .LBB0_2: # %bb71167 There's an obviously unnecessary movl in .LBB0_2, and we could eliminate a1243 jne LBB0_21817 je LBB0_21821 LBB0_2: ## %if.end1878 jae .LBB0_21967 je LBB0_21973 je LBB0_2
1084 LBB0_2: ## %for.body1096 jne LBB0_21782 .LBB0_2:1791 ja .LBB0_21793 .LBB0_2:2317 je .LBB0_22323 .LBB0_2: # %if.else