From: "H . J . Lu" <hjl@lucon.org>
To: amodra@one.net.au
Cc: binutils@sourceware.cygnus.com
Subject: Re: "make check" failures with ia64-linux
Date: Sun, 27 May 2001 00:58:00 -0000 [thread overview]
Message-ID: <20010527005810.B30645@lucon.org> (raw)
In-Reply-To: <20010526232121.E10344@squeak.one.net.au>
On Sat, May 26, 2001 at 11:21:21PM +0930, amodra@one.net.au wrote:
> On Fri, May 25, 2001 at 05:30:30PM -0700, H . J . Lu wrote:
> > I got 4 "make check" failures with ia64-linux. In gas
> >
> > FAIL: elf ehopt0
> > FAIL: ia64 dv-raw-err
> > FAIL: ia64 dv-waw-err
> >
> > In binutils
> >
> > FAIL: readelf -s
> >
> > There used to be no failures with ia64-linux.
>
> Can you pinpoint when the failures started occurring? My changes
> to symbol resolution dating back to 2001-03-30 might have
> destabilised the assembler.
The last working one is 2.11.90.0.1, which is based on CVS of
Mar 9, 2001. 2.11.90.0.4 based on Apr. 1, 2001 has
FAIL: readelf -s
2.11.90.0.5 based on Apr. 14, 2001 has
FAIL: readelf -s
FAIL: ia64 dv-raw-err
FAIL: ia64 dv-waw-err
ehopt0 was added on May 14. It looks like
/export/build/gnu/binutils/build-ia64-linux/gas/testsuite/../../binutils/objdump -s -j .eh_frame dump.o > dump.out
regexp_diff match failure
regexp "^ 0+010 (01|00)0000(00|01) (12|00)0000(00|12) (18|00)0000(00|18) 00000000 .*$"
line " 0010 01000000 18000000 18000000 00000000 ................"
regexp_diff match failure
regexp "^ 0+020 (08|00)0000(00|08) 04(08|00)0000 (00|08)44 .*$"
line " 0020 08000000 04000000 08000000 44000000 ............D..."
FAIL: elf ehopt0
Sorry I don't have more time for ia64.
H.J.
next prev parent reply other threads:[~2001-05-27 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 17:30 H . J . Lu
[not found] ` <20010526232121.E10344@squeak.one.net.au>
2001-05-27 0:58 ` H . J . Lu [this message]
2001-05-27 7:15 ` amodra
2001-05-27 9:51 ` H . J . Lu
2001-05-28 19:23 ` George France
2001-05-28 19:33 ` H . J . Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010527005810.B30645@lucon.org \
--to=hjl@lucon.org \
--cc=amodra@one.net.au \
--cc=binutils@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).