From: "H. J. Lu" <hjl@lucon.org>
To: joern.rennecke@superh.com
Cc: binutils@sources.redhat.com
Subject: Re: Why so many failures for Linux/sh64?
Date: Wed, 23 Jul 2003 14:19:00 -0000 [thread overview]
Message-ID: <20030723141906.GA15708@lucon.org> (raw)
In-Reply-To: <20030723054606.GB7579@lucon.org>
On Tue, Jul 22, 2003 at 10:46:06PM -0700, H. J. Lu wrote:
> On Tue, Jul 22, 2003 at 10:44:10PM -0700, H. J. Lu wrote:
> > I got many
> >
> > /export/build/linux/binutils/build-sh64-linux/gas/testsuite/../../binutils/objdump:
> > Matching formats: elf32-sh64big-linux elf32-sh64
> > FAIL: SH PIC constructs
> >
Why do we need so many elf32/sh64 targets? What are differences
between NetBSD/sh64 and Linux/sh64? Can't we set ELF_MAXPAGESIZE
and elf_symbol_leading_char based on target and share one elf32/sh64
target? They can have a default and we can change them from outside.
H.J.
next prev parent reply other threads:[~2003-07-23 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:44 H. J. Lu
2003-07-23 5:46 ` H. J. Lu
2003-07-23 6:08 ` kaz Kojima
2003-07-23 14:19 ` H. J. Lu [this message]
2003-07-23 17:26 ` Joern Rennecke
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=20030723141906.GA15708@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=joern.rennecke@superh.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).