This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: on sparc-linux: FAIL: ld-elf/loadaddr2

On Mon, Aug 21, 2006 at 10:13:55AM +0200, Christian Joensson wrote:
> On 8/21/06, Christian Joensson <> wrote:
> >I just tried binutils daily snapshot, 20060821, and found a new
> >testsuite failure, not present on the 20060818 snapshot, siince it was
> >added 20060818...
> bah, a mixup, it should have been
> >/usr/local/src/trunk/objdir-binutils32/ld/../gas/as-new    -o
> >tmpdir/dump0.o /usr/local/src/trunk/src/ld/testsuite/ld-elf/loadaddr.s
> >./ld-new  -L/usr/local/src/trunk/src/ld/testsuite/ld-elf  -T
> >loadaddr2.t -z max-page-size=0x200000 -o tmpdir/dump tmpdir/dump0.o
> >/usr/local/src/trunk/objdir-binutils32/ld/../binutils/readelf  -l
> >--wide tmpdir/dump > tmpdir/dump.out
> >regexp_diff match failure
> >regexp "^  LOAD +0x302000 0xf*80302000 0xf*80302000 0x0*1 0x0*1 RW  
> >0x200000$"
> >line   "  LOAD           0x302000 0x80302000 0x802f3000 0x00001
> >0x00001 RW  0x200000"
> >FAIL: ld-elf/loadaddr2
> >
> >Any ideas of what is wrong?
> >
> >Would you like me to provide more informaton?
> >

It is

The documented behavior of setting output section's load memory address


has been changed, depending on the lma/vma of the previous output
section. The documented behavior is at least used by the x86-64
Linix kernel. There are 2 different usages of the documented
behavior. The one used by the x86-64 Linix kernel is fixed. But the
other one isn't. I believe that it is a regression if the document
isn't updated. That is the failure you saw.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]