From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
"Kevin D. Kissell" <kevink@mips.com>,
linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: [patch] linux: cpu_probe(): remove 32-bit CPU bits for MIPS64
Date: Wed, 24 Jul 2002 16:52:39 +0200 [thread overview]
Message-ID: <20020724165239.F28010@dea.linux-mips.net> (raw)
In-Reply-To: <3D3DC6E6.AFF9CBFD@mips.com>; from kevink@mips.com on Tue, Jul 23, 2002 at 02:13:10PM -0700
Maciej,
> I don't think it's possible to be fully achieved. Some differences will
> have to exist, at least in the headers, but likely within the arch tree as
> well. The reason is binary code size or perfomance -- having R3000
> support code in mips64 binaries is simply ridiculous as is using 32-bit
> operations with 64-bit data on a 64-bit CPU. However, it is worth trying
> to minimize visible differences where possible, e.g. by convincing the
> compiler to optimize irrelevant bits away.
In this particular case all the bloat is just in __init code, could that
convince you?
Ralf
next prev parent reply other threads:[~2002-07-24 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 11:55 [patch] linux: cpu_probe(): remove 32-bit CPU bits for MIPS64 Maciej W. Rozycki
2002-07-23 12:14 ` Ralf Baechle
2002-07-23 13:05 ` Maciej W. Rozycki
2002-07-23 13:23 ` Ralf Baechle
2002-07-23 13:31 ` Maciej W. Rozycki
2002-07-23 13:59 ` Ralf Baechle
2002-07-23 18:20 ` Jun Sun
2002-07-24 15:11 ` Maciej W. Rozycki
2002-07-23 14:38 ` Kevin D. Kissell
2002-07-23 14:38 ` Kevin D. Kissell
2002-07-23 14:49 ` Ralf Baechle
2002-07-23 16:00 ` Maciej W. Rozycki
2002-07-23 21:13 ` Kevin D. Kissell
2002-07-24 14:52 ` Ralf Baechle [this message]
2002-07-24 15:05 ` Maciej W. Rozycki
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=20020724165239.F28010@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=kevink@mips.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--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