From: "Stephen Clarke" <stephen.clarke@earthling.net>
To: "H. J. Lu" <hjl@lucon.org>
Cc: <binutils@sources.redhat.com>
Subject: Re: [Patch] sh64: Fix gas testsuite expected output
Date: Tue, 15 Oct 2002 20:16:00 -0000 [thread overview]
Message-ID: <002e01c2749c$e15e2980$6301a8c0@wren> (raw)
From: "Stephen Clarke"
Sent: Monday, October 14, 2002 10:05 PM
>
> From: "H. J. Lu"
> Sent: Monday, October 14, 2002 9:38 PM
>
> > [long list of further failures]
>
> I don't get any of these. I'll try to work out why.
> It could help if you'd send me the gas.log file.
It looks like these failures are because of:
.../objdump: dump.o: File format is ambiguous
.../objdump: Matching formats: elf32-sh64big-linux elf32-sh64
and that's because both sh-linux and sh64-linux targets
are enabled, i.e. binutils is configured with
--enable-targets=...,sh-linux,sh64-linux,...
The definition of sh-*-linux* in config.bfd is:
sh-*-linux*)
targ_defvec=bfd_elf32_shblin_vec
targ_selvecs=bfd_elf32_shlin_vec
#ifdef BFD64
targ_selvecs="${targ_selvecs} bfd_elf32_sh64_vec bfd_elf32_sh64l_vec bfd_elf64_sh64_vec bfd_elf64_sh64l_vec"
#endif
This includes some "sh64" target vectors, which then cannot be distinguished
from sh64-linux target vectors.
I'm not sure why sh-*-linux* should include sh64 target vectors. My understanding
of "sh" is that it is supposed to be 32-bit sh targets only, and it
should avoid any overhead required for 64-bit targets.
I suggest that the sh64 vectors are removed from sh-*-linux*.
What do the maintainers think?
(Aside: as mentioned in http://sources.redhat.com/ml/binutils/2002-08/msg00069.html
this particular use of ifdef BFD64 has no effect in config.bfd: the sh64 vectors are
built into an sh-linux target whether or not --enable-64-bit-bfd is specified. I intended to
submit a patch to strip out the ineffectual ifdefs, but forgot.)
Steve.
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
next reply other threads:[~2002-10-16 3:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 20:16 Stephen Clarke [this message]
2002-10-15 20:27 ` H. J. Lu
2002-10-15 21:39 ` Stephen Clarke
2002-10-15 22:32 ` H. J. Lu
2002-10-15 22:54 ` Stephen Clarke
2002-10-15 23:00 ` H. J. Lu
2002-10-15 23:39 ` H. J. Lu
2002-10-16 1:47 ` Alan Modra
2002-10-16 6:16 ` H. J. Lu
2002-10-16 8:03 ` Alan Modra
2002-10-16 8:14 ` H. J. Lu
2002-10-16 9:50 ` Matt Thomas
2002-10-18 1:56 ` Alan Modra
2002-10-18 10:22 ` Ulrich Drepper
2002-10-18 10:38 ` H. J. Lu
2002-10-18 11:21 ` Jason R Thorpe
2002-10-18 11:27 ` Jason R Thorpe
2002-10-18 12:33 ` Hans-Peter Nilsson
2002-10-18 18:04 ` Alan Modra
2002-10-18 18:46 ` Hans-Peter Nilsson
2002-10-22 1:44 ` kaz Kojima
2002-10-22 10:14 ` Change ELFOSABI in SH (Re: [Patch] sh64: Fix gas testsuite expected output) H. J. Lu
2002-10-22 15:58 ` kaz Kojima
2002-10-22 16:43 ` Hans-Peter Nilsson
2002-10-22 22:55 ` Jason R Thorpe
2002-10-22 22:58 ` H. J. Lu
2002-10-23 5:12 ` kaz Kojima
2002-10-15 21:51 ` [Patch] sh64: Fix gas testsuite expected output Hans-Peter Nilsson
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 16:00 Stephen Clarke
2002-10-02 16:05 ` Hans-Peter Nilsson
2002-10-02 16:08 ` H. J. Lu
2002-10-02 16:28 ` Stephen Clarke
2002-10-02 17:00 ` Hans-Peter Nilsson
2002-10-02 17:12 ` Hans-Peter Nilsson
2002-10-09 13:34 ` Stephen Clarke
2002-10-09 21:20 ` Hans-Peter Nilsson
2002-10-11 10:51 ` Stephen Clarke
2002-10-13 22:01 ` Hans-Peter Nilsson
2002-10-02 17:04 ` H. J. Lu
2002-10-14 21:14 ` Stephen Clarke
2002-10-14 21:38 ` H. J. Lu
2002-10-14 22:05 ` Stephen Clarke
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='002e01c2749c$e15e2980$6301a8c0@wren' \
--to=stephen.clarke@earthling.net \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
/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).