[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/2378] Incorrect opcode in __do_clear_bss if bss has more than 15
KenJackson at ieee dot org
[Bug ld/2378] Incorrect opcode in __do_clear_bss if bss has more than 15 bytes
22 Feb 2006 14:52:32 -0000
------- Additional Comments From KenJackson at ieee dot org 2006-02-22 14:52
I've simplified it by stripping away all gcc influence. This is purely
a binutils bug. I suspect it is ld's relocation that is causing the
problem. Or maybe it's the BFD library, if that's a separate entity.
Source file, a.S:
avr-as a.S -o a.o
avr-ld -m avr4 -Tdata 0x800100 -o a.elf a.o
avr-objdump -d a.elf > a.lst
avr-ld -m avr4 -Tdata 0x800100 -o a.hex --oformat=ihex a.o
Output file a.lst, lines 7,8:
0: a0 31 cpi r26, 0x10 ; 16
2: a0 31 cpi r26, 0x10 ; 16
Output file a.hex:
The list file shows both opcodes correctly, "a0 31". But in the hex file
the first one is wrong, "B031", while the second one is correct, "A031".
The difference is that avr-ld had to do a relocation for the first one.
Running "avr-objdump -r a.o" shows one record with type R_AVR_LO8_LDI
relocation, value __bss_end.
R_AVR_LO8_LDI is performed in binutils-2.16.1/bfd/elf32-avr.c. It works
correctly for the default ELF format, but fails for the IHEX format.
This is progress, but I'm still stumped.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.