From: Daniel Jacobowitz <dan@debian.org>
To: Eric Christopher <echristo@redhat.com>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
Alexandre Oliva <aoliva@redhat.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Atsushi Nemoto <nemoto@toshiba-tops.co.jp>,
linux-mips@linux-mips.org, binutils@sources.redhat.com
Subject: Re: recent binutils and mips64-linux
Date: Tue, 23 Sep 2003 14:16:59 -0400 [thread overview]
Message-ID: <20030923181659.GA30037@nevyn.them.org> (raw)
In-Reply-To: <1064340070.21720.14.camel@ghostwheel.sfbay.redhat.com>
On Tue, Sep 23, 2003 at 11:01:11AM -0700, Eric Christopher wrote:
>
> > >
> > > objcopy?
> >
> > You mean, let gcc generate n64 code, stuff it in n32 objects, and
> > objcopy it back to n64? Well, it may work, but it looks more like
> > a test of binutils sign-extension handling than a straightforward
> > way of creating kernels to me.
> >
> > Besides, as soon as gcc handles 64bit expansions itself we need
> > such an option anyway.
>
> I'm still trying to figure out why you are going through such weird
> contortions at all. I understand not having an elf64 loader. That's what
> the objcopy comment was for, everything else I don't understand. Why not
> compile for the abi you want?
Compare the optimal way to load an address into a register when you
have a full 64-bit address space and when you know that addresses are
sign extended. I'm told it saves over 100K of code.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-23 18:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 21:27 recent binutils and mips64-linux Daniel Jacobowitz
2003-09-19 2:58 ` Eric Christopher
2003-09-19 3:29 ` Atsushi Nemoto
2003-09-19 3:28 ` Daniel Jacobowitz
2003-09-19 7:23 ` Atsushi Nemoto
2003-09-19 5:39 ` Eric Christopher
2003-09-19 12:52 ` Maciej W. Rozycki
2003-09-19 16:20 ` Eric Christopher
2003-09-19 16:41 ` Thiemo Seufer
2003-09-19 16:46 ` Maciej W. Rozycki
2003-09-19 17:08 ` Thiemo Seufer
2003-09-19 17:19 ` Maciej W. Rozycki
2003-09-19 17:40 ` Thiemo Seufer
2003-09-19 18:14 ` Maciej W. Rozycki
2003-09-19 18:28 ` David Kesselring
2003-09-22 21:26 ` Alexandre Oliva
2003-09-22 21:31 ` Daniel Jacobowitz
2003-09-22 23:39 ` Thiemo Seufer
2003-09-23 1:21 ` Eric Christopher
2003-09-23 8:14 ` Thiemo Seufer
2003-09-23 18:01 ` Eric Christopher
2003-09-23 18:16 ` Daniel Jacobowitz [this message]
2003-09-23 19:45 ` Zack Weinberg
2003-09-23 19:56 ` Daniel Jacobowitz
2003-09-23 20:03 ` Thiemo Seufer
2003-09-23 20:06 ` Zack Weinberg
2003-09-23 20:18 ` Thiemo Seufer
2003-09-23 20:28 ` Eric Christopher
2003-09-19 16:42 ` Maciej W. Rozycki
2003-09-19 16:57 ` Thiemo Seufer
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=20030923181659.GA30037@nevyn.them.org \
--to=dan@debian.org \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=nemoto@toshiba-tops.co.jp \
/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