mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-01-06 12:09:26 +08:00
05805feba2
This fixes the testcases that are failing due to my recent patch. It turns out that the start address across baremetal and linux builds isn't entirely predictable without a linker script. Since the address themselves are not the important thing I am ignoring them now. Secondly I was encoding data using .word using non 0 values, however because .word is subjected to endiannes these non-zero values under big-endian happen to fall into the encoding space of instructions which changes the disassembly. Using 0 fixes this problem and the purpose of the test still holds, though objdump will dump ... for data only sections, which is ok as the data/insn mixed sections will test the patch. The ARM Attributes sections is not important and is ignored. binutils/ChangeLog: * testsuite/binutils-all/aarch64/in-order.d: Likewise. * testsuite/binutils-all/aarch64/out-of-order-all.d: Likewise. * testsuite/binutils-all/aarch64/out-of-order.d: Likewise. * testsuite/binutils-all/aarch64/out-of-order.s: Likewise. * testsuite/binutils-all/arm/in-order-all.d: Likewise. * testsuite/binutils-all/arm/in-order.d: Likewise. * testsuite/binutils-all/arm/out-of-order-all.d: Likewise. * testsuite/binutils-all/arm/out-of-order.d: Likewise. * testsuite/binutils-all/arm/out-of-order.s: Likewise.
30 lines
386 B
ArmAsm
30 lines
386 B
ArmAsm
.text
|
|
.arm
|
|
.global v1
|
|
.section .func1,"ax",%progbits
|
|
.type v1 %function
|
|
.size v1, 4
|
|
v1:
|
|
add r0, r0, r1
|
|
.word 0
|
|
|
|
.section .func2,"ax",%progbits
|
|
add r0, r0, r1
|
|
|
|
.section .func3,"ax",%progbits
|
|
add r0, r0, r1
|
|
add r0, r0, r1
|
|
add r0, r0, r1
|
|
add r0, r0, r1
|
|
add r0, r0, r1
|
|
.word 0
|
|
|
|
.data
|
|
.section .global,"aw",%progbits
|
|
.word 0
|
|
.word 0
|
|
.word 0
|
|
|
|
.section .rodata
|
|
.word 0
|