llvm/test/CodeGen/X86/win32-pic-jumptable.ll
Matthias Braun 26256fb2f9 MCStreamer: Use "cfi" for CFI related temp labels.
Choosing a "cfi" name makes the intend a bit clearer in an assembly dump
and more importantly the assembly dumps are slightly more stable as the
numbers don't move around anymore when unrelated code calls
createTempSymbol() more or less often.
As they are temp labels the name doesn't influence the generated object
code.

Differential Revision: https://reviews.llvm.org/D27244

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@288290 91177308-0d34-0410-b5e6-96231b3b80d8
2016-11-30 23:48:26 +00:00

41 lines
879 B
LLVM

; RUN: llc < %s -relocation-model=pic | FileCheck %s
; CHECK: calll L0$pb
; CHECK-NEXT: Lcfi{{[0-9]+}}:
; CHECK-NEXT: .cfi_adjust_cfa_offset 4
; CHECK-NEXT: L0$pb:
; CHECK-NEXT: popl %eax
; CHECK-NEXT: Lcfi{{[0-9]+}}:
; CHECK-NEXT: .cfi_adjust_cfa_offset -4
; CHECK-NEXT: addl LJTI0_0(,%ecx,4), %eax
; CHECK-NEXT: jmpl *%eax
; CHECK: LJTI0_0:
; CHECK-NEXT: .long LBB0_2-L0$pb
; CHECK-NEXT: .long LBB0_3-L0$pb
; CHECK-NEXT: .long LBB0_4-L0$pb
; CHECK-NEXT: .long LBB0_5-L0$pb
target triple = "i686--windows-itanium"
define i32 @f(i64 %x) {
bb0:
switch i64 %x, label %bb5 [
i64 1, label %bb1
i64 2, label %bb2
i64 3, label %bb3
i64 4, label %bb4
]
bb1:
br label %bb5
bb2:
br label %bb5
bb3:
br label %bb5
bb4:
br label %bb5
bb5:
%y = phi i32 [ 0, %bb0 ], [ 1, %bb1 ], [ 2, %bb2 ], [ 3, %bb3 ], [ 4, %bb4 ]
ret i32 %y
}