* on sparc-linux: FAIL: ld-elf/loadaddr2
@ 2006-08-21 8:14 Christian Joensson
2006-08-21 10:01 ` Christian Joensson
0 siblings, 1 reply; 5+ messages in thread
From: Christian Joensson @ 2006-08-21 8:14 UTC (permalink / raw)
To: binutils
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
I just tried binutils daily snapshot, 20060821, and found a new
testsuite failure, not present on the 20060818 snapshot, siince it was
added 20060818... http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00792.html
/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?
--
Cheers,
/ChJ
[-- Attachment #2: test.txt --]
[-- Type: text/plain, Size: 1380 bytes --]
Aurora SPARC Linux release 2.0 (Kashmir FC3)/TI UltraSparc IIi (Sabre) sun4u:
binutils-2.15.92.0.2-5.1.sparc
bison-1.875c-2.sparc
dejagnu-1.4.4-2.noarch
expect-5.42.1-1.sparc
gcc-3.4.2-6.fc3.sparc
glibc-2.3.6-0.fc3.1.sparcv9
glibc-2.3.6-0.fc3.1.sparc64
glibc-devel-2.3.6-0.fc3.1.sparc
glibc-devel-2.3.6-0.fc3.1.sparc64
glibc-headers-2.3.6-0.fc3.1.sparc
glibc-kernheaders-2.6-20sparc.sparc
gmp-4.1.4-3sparc.sparc
gmp-4.1.4-3sparc.sparc64
gmp-devel-4.1.4-3sparc.sparc
gmp-devel-4.1.4-3sparc.sparc64
kernel-2.6.13-1.1603sp13.sparc64
libgcc-3.4.2-6.fc3.sparc
libgcc-3.4.2-6.fc3.sparc64
libgcj-3.4.2-6.fc3.sparc
libgcj-devel-3.4.2-6.fc3.sparc
libstdc++-3.4.2-6.fc3.sparc
libstdc++-3.4.2-6.fc3.sparc64
libstdc++-devel-3.4.2-6.fc3.sparc
make-3.80-5.sparc
tcl-8.4.7-2.sparc
LAST_UPDATED: 060821 20060821
Native configuration is sparc-unknown-linux-gnu
=== binutils tests ===
Running target unix
=== binutils Summary ===
# of expected passes 40
=== gas tests ===
Running target unix
=== gas Summary ===
# of expected passes 120
# of expected failures 1
=== ld tests ===
Running target unix
FAIL: ld-elf/loadaddr2
=== ld Summary ===
# of expected passes 327
# of unexpected failures 1
# of expected failures 5
version: 060821 20060821
Platform: sparc-unknown-linux-gnu
configure flags: sparc-linux --enable-__cxa_atexit --enable-shared --enable-64-bit-bfd
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: on sparc-linux: FAIL: ld-elf/loadaddr2
2006-08-21 8:14 on sparc-linux: FAIL: ld-elf/loadaddr2 Christian Joensson
@ 2006-08-21 10:01 ` Christian Joensson
2006-08-22 0:17 ` H. J. Lu
0 siblings, 1 reply; 5+ messages in thread
From: Christian Joensson @ 2006-08-21 10:01 UTC (permalink / raw)
To: binutils; +Cc: H. J. Lu
On 8/21/06, Christian Joensson <christian.joensson@gmail.com> 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... http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00792.html
bah, a mixup, it should have been
http://sourceware.org/ml/binutils-cvs/2006-08/msg00093.html
> /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?
>
--
Cheers,
/ChJ
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: on sparc-linux: FAIL: ld-elf/loadaddr2
2006-08-21 10:01 ` Christian Joensson
@ 2006-08-22 0:17 ` H. J. Lu
2006-08-22 13:02 ` Christian Joensson
0 siblings, 1 reply; 5+ messages in thread
From: H. J. Lu @ 2006-08-22 0:17 UTC (permalink / raw)
To: Christian Joensson; +Cc: binutils
On Mon, Aug 21, 2006 at 10:13:55AM +0200, Christian Joensson wrote:
> On 8/21/06, Christian Joensson <christian.joensson@gmail.com> 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... http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00792.html
>
> bah, a mixup, it should have been
> http://sourceware.org/ml/binutils-cvs/2006-08/msg00093.html
>
> >/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
http://sources.redhat.com/bugzilla/show_bug.cgi?id=3052
The documented behavior of setting output section's load memory address
in
SECTION :
{
}
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.
H.J.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: on sparc-linux: FAIL: ld-elf/loadaddr2
2006-08-22 0:17 ` H. J. Lu
@ 2006-08-22 13:02 ` Christian Joensson
2006-08-22 17:36 ` Alan Modra
0 siblings, 1 reply; 5+ messages in thread
From: Christian Joensson @ 2006-08-22 13:02 UTC (permalink / raw)
To: H. J. Lu; +Cc: binutils, Alan Modra
hmm, with the patch
http://sourceware.org/ml/binutils-cvs/2006-08/msg00110.html, I get two
failures:
/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
loadaddr1.t -z max-page-size=0x200000 -o tmpdir/dump tmpdir/dump0.o
succeeded with: <lt-ld-new: warning: dot moved backwards before `.data'
lt-ld-new: warning: dot moved backwards before `.data'
lt-ld-new: warning: dot moved backwards before `.data'>, expected: <>
lt-ld-new: warning: dot moved backwards before `.data'
lt-ld-new: warning: dot moved backwards before `.data'
lt-ld-new: warning: dot moved backwards before `.data'
succeeded with: <lt-ld-new: warning: dot moved backwards before `.data'
lt-ld-new: warning: dot moved backwards before `.data'
lt-ld-new: warning: dot moved backwards before `.data'>, expected: <>
FAIL: ld-elf/loadaddr1
/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
without the patch, I only get the second failure
On 8/21/06, H. J. Lu <hjl@lucon.org> wrote:
> On Mon, Aug 21, 2006 at 10:13:55AM +0200, Christian Joensson wrote:
> > On 8/21/06, Christian Joensson <christian.joensson@gmail.com> 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... http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00792.html
> >
> > bah, a mixup, it should have been
> > http://sourceware.org/ml/binutils-cvs/2006-08/msg00093.html
> >
> > >/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
>
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=3052
>
> The documented behavior of setting output section's load memory address
> in
>
> SECTION :
> {
> }
>
> 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.
>
>
> H.J.
>
--
Cheers,
/ChJ
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-08-22 13:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-08-21 8:14 on sparc-linux: FAIL: ld-elf/loadaddr2 Christian Joensson
2006-08-21 10:01 ` Christian Joensson
2006-08-22 0:17 ` H. J. Lu
2006-08-22 13:02 ` Christian Joensson
2006-08-22 17:36 ` Alan Modra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).