http://llvm.org/bugs/show_bug.cgi?id=18231
Bug ID: 18231
Summary: Unwind code in Android uses .code 32 in inline
assembly
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Backend: ARM
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Classification: Unclassified
A feature recently being introduced to avoid the madness of having .arm/.thumb
(.code 32/.code 16) in inline assembly will break the Android build because the
unwind code uses that extensively.
Here's a snippet. As you can see, the function is Thumb (.code 16), the inline
ASM changes it to ARM (.code 32), than the function continues and returns with
an instruction that is only valid in Thumb mode (pop.w).
.section .text._ZN13UnwindCurrent6UnwindEj,"ax",%progbits
.globl _ZN13UnwindCurrent6UnwindEj
.align 2
.type _ZN13UnwindCurrent6UnwindEj,%function
.code 16
.thumb_func
_ZN13UnwindCurrent6UnwindEj:
.Lfunc_begin3:
.loc 1 66 0
.loc 1 0 0
push.w {r11, lr}
mov r2, r0
.Ltmp7:
.loc 1 67 0 prologue_end
add.w r0, r2, #8
.Ltmp8:
@APP
.align 2
bx pc
nop
.code 32
stmia r0, {r0-r15}
orr r0, pc, #1
bx r0
@NO_APP
.Ltmp9:
.loc 1 72 0
mov r0, r2
movs r2, #1
.Ltmp10:
bl _ZN13UnwindCurrent17UnwindFromContextEjb(PLT)
.loc 1 73 0
pop.w {r11, pc}
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
