From: Hans-Peter Nilsson <hp@bitrange.com>
To: Stephen Clarke <stephen.clarke@earthling.net>
Cc: "H. J. Lu" <hjl@lucon.org>, <binutils@sources.redhat.com>
Subject: Re: [Patch] sh64: Fix gas testsuite expected output
Date: Tue, 15 Oct 2002 21:51:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0210160042290.65920-100000@dair.pair.com> (raw)
In-Reply-To: <002e01c2749c$e15e2980$6301a8c0@wren>
On Tue, 15 Oct 2002, Stephen Clarke wrote:
> 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.
For "sh" as opposed to "sh4" an other variants, the default is
to include the sh64 vectors, so sh-*-* tools can identify and
interpret sh64 objects. GDB folks in particular like this.
> I suggest that the sh64 vectors are removed from sh-*-linux*.
> What do the maintainers think?
No, we've been through that before, summarized above.
As H.J. noted, the ambiguity bug is not solved by excluding
vectors. The elf32-sh64big-linux and elf32-sh64 targets must be
disambiguated somehow; there should be some ELF header info that
tells them apart. If there is nothing to tell them apart,
something should be added.
brgds, H-P
next prev parent reply other threads:[~2002-10-16 4:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 20:16 Stephen Clarke
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 ` Hans-Peter Nilsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 16:00 [Patch] sh64: Fix gas testsuite expected output 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=Pine.BSF.4.44.0210160042290.65920-100000@dair.pair.com \
--to=hp@bitrange.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=stephen.clarke@earthling.net \
/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).