This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: V850, linker script problem
Hi,
i did some more tests:
A:
at the moment i use binutils-2.16.1. I also tried 2.16 and 2.15.
They show the same behaviour, 2.15 even aborts with
"Speicherzugriffsfehler" (bus error?).
B:
I added another section for testing:
.myqwe :
{
*(.myqwe)
} > ram AT > rom
in vectors.S:
.section .myqwe,"w"
.string "abcdefg"
It leads to exactly the behaviour i expect:
.myqwe 0x03ffe000 0x8 load address 0x00000678
*(.myqwe)
.myqwe 0x03ffe000 0x8 vectors.o
I wonder why defining the sections the same way does not work
for ".sdata" and for ".tdata".
C:
The sections .sdata and .tdata are empty, but also when i add
some data to it it results in the same error message.
Also, i wonder how the flags for those sections ".sdata" and
".tdata" are set. Where do the flags come from? Could this
influence the problem?
In main.c:
int __attribute__((section(".sdata"))) abc = 7;
The output of readelf -S shows for .sdata:
Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf
Al
[ 0] NULL 00000000 000000 000000 00 0 0
0
[ 1] .text PROGBITS 00000000 000034 000036 00 AX 0 0
2
[ 2] .data PROGBITS 00000000 00006a 000000 00 WA 0 0
1
[ 3] .bss NOBITS 00000000 00006a 000000 00 WA 0 0
1
[ 4] .sdata PROGBITS 00000000 00006c 000004 00 WA 0 0
4
[ 5] .comment PROGBITS 00000000 000070 000012 00 0 0
1
[ 6] .shstrtab STRTAB 00000000 000082 00003c 00 0 0
1
[ 7] .symtab SYMTAB 00000000 000228 000090 10 8 7
4
[ 8] .strtab STRTAB 00000000 0002b8 000013 00 0 0
1
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings)
I (info), L (link order), G (group), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)
It would be great if anybody would have a hint for me.
Best regards,
Torsten.