From: "H. J. Lu" <hjl@lucon.org>
To: Stephen Clarke <stephen.clarke@earthling.net>
Cc: binutils@sources.redhat.com
Subject: Re: [Patch] sh64: Fix gas testsuite expected output
Date: Tue, 15 Oct 2002 23:39:00 -0000 [thread overview]
Message-ID: <20021015233936.A29638@lucon.org> (raw)
In-Reply-To: <20021015230020.A29100@lucon.org>; from hjl@lucon.org on Tue, Oct 15, 2002 at 11:00:20PM -0700
On Tue, Oct 15, 2002 at 11:00:20PM -0700, H. J. Lu wrote:
> On Tue, Oct 15, 2002 at 10:51:59PM -0700, Stephen Clarke wrote:
> > From: "H. J. Lu" <hjl@lucon.org>
> > Sent: Tuesday, October 15, 2002 10:32 PM
> >
> >
> > > On Tue, Oct 15, 2002 at 09:39:29PM -0700, Stephen Clarke wrote:
> > > > From: "H. J. Lu"
> > > > Sent: Tuesday, October 15, 2002 8:27 PM
> > > > >
> > > > > That is not right. Something is wrong with ELF/SH. Can you tell me
> > > > > the difference between elf32-sh64big-linux and elf32-sh64 in the
> > > > > ELF header?
> > > >
> > > > I can't: I don't think there is a difference in the ELF header.
> > > > The same issue applies to non-sh64 targets,
> > > > e.g.elf32-shl and elf32-sh-linux.
> > > >
> > >
> > > Then, I have to ask, what are the differences between elf32-shl and
> > > elf32-sh-linux? If you tell me that, I may come up with something.
> >
> > If you mean what are the differences in the ELF header between
> > elf32-shl and elf32-sh-linux, then I don't think there are any. If I
>
> No, why do you have elf32-shl and elf32-sh-linux? Can you just use
> elf32-shl for Linux?
>
It looks like Linux/sh uses a different ABI than ELF/sh. Please
consider setting ELFOSABI_LINUX. See elf32-hppa.c/elf64-hppa.c
for how to do it. You should do it ASAP before it is too late.
H.J.
next prev parent reply other threads:[~2002-10-16 6:39 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 [this message]
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=20021015233936.A29638@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--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).