From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Carsten Langgaard <carstenl@mips.com>,
"Kevin D. Kissell" <kevink@mips.com>,
linux-mips@linux-mips.org
Subject: Re: Latest sources from CVS.
Date: Fri, 6 Dec 2002 18:02:41 +0100 [thread overview]
Message-ID: <20021206180241.A7492@linux-mips.org> (raw)
In-Reply-To: <20021206164558.GH23743@rembrandt.csv.ica.uni-stuttgart.de>; from ica2_ts@csv.ica.uni-stuttgart.de on Fri, Dec 06, 2002 at 05:45:58PM +0100
On Fri, Dec 06, 2002 at 05:45:58PM +0100, Thiemo Seufer wrote:
> > If we want to preserve the setup cleanly, we
> > probably need yet another ABI model in gcc (especially in the face of the
> > coming changes to get rid of assembly macros), with sign-extended 32-bit
> > pointers for accessing program segments and 64-bit ones for the remaining
> > addresses.
>
> Do you think this is worth the hassle? N64 offers better flexibility in
> the large memory case at some performance cost, and it's conceptionally
> cleaner.
Absolutely:
[ralf@dea linux-sgi-2.4]$ mips64-linux-size vmlinux
text data bss dec hex filename
1978296 317344 156224 2451864 256998 vmlinux
[ralf@dea linux-sgi-2.4]$ mips64-linux-size vmlinux
text data bss dec hex filename
1761168 317344 156224 2234736 221970 vmlinux
The first kernel was built as 64-bit ELF using 64-bit pointer and everything
64-bit. The second kernel was built using the -Wa,-32 trick. That's over
12% of bloat for full 64-bitiness which brings zero gain.
Ralf
next prev parent reply other threads:[~2002-12-06 17:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 8:34 Latest sources from CVS Carsten Langgaard
2002-12-04 9:09 ` Kevin D. Kissell
2002-12-04 9:09 ` Kevin D. Kissell
2002-12-04 13:04 ` Ralf Baechle
2002-12-05 3:34 ` Ralf Baechle
2002-12-05 11:14 ` Carsten Langgaard
2002-12-05 13:47 ` Maciej W. Rozycki
2002-12-05 14:12 ` Carsten Langgaard
2002-12-05 14:27 ` Ralf Baechle
2002-12-06 12:52 ` Carsten Langgaard
2002-12-06 13:07 ` Ralf Baechle
2002-12-06 13:24 ` Carsten Langgaard
2002-12-06 13:24 ` Thiemo Seufer
2002-12-06 13:34 ` Thiemo Seufer
2002-12-06 13:41 ` Carsten Langgaard
2002-12-06 13:51 ` Thiemo Seufer
2002-12-06 16:32 ` Maciej W. Rozycki
2002-12-06 16:45 ` Thiemo Seufer
2002-12-06 17:01 ` Maciej W. Rozycki
2002-12-06 17:24 ` Thiemo Seufer
2002-12-06 18:04 ` Ralf Baechle
2002-12-06 18:30 ` Maciej W. Rozycki
2002-12-06 18:41 ` Thiemo Seufer
2002-12-06 18:58 ` Maciej W. Rozycki
2002-12-06 17:02 ` Ralf Baechle [this message]
2002-12-06 17:15 ` Thiemo Seufer
2002-12-06 17:34 ` Greg Lindahl
2002-12-06 18:18 ` Dominic Sweetman
2002-12-06 18:40 ` Greg Lindahl
2002-12-06 23:17 ` Ralf Baechle
2002-12-06 23:33 ` Thiemo Seufer
2002-12-07 0:00 ` Ralf Baechle
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=20021206180241.A7492@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=carstenl@mips.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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