From: "Stephen P. Becker" <geoman@gentoo.org>
To: Robin Humble <rjh@cita.utoronto.ca>
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel 2.6 for R4600 Indy
Date: Fri, 24 Sep 2004 11:13:18 -0400 [thread overview]
Message-ID: <4154398E.3070806@gentoo.org> (raw)
In-Reply-To: <20040924134334.GB27739@lemming.cita.utoronto.ca>
>>day). Also, Indys don't support a large enough memory configuration
>>that 64-bit would be worth it anyhow.
>
>
> indeed they don't.
> do you get access to more registers or more efficient instruction sets
> like you do on x86_64?
>
>
>>What you would *really* want on such a machine would be n32 userland.
>>You get full 64-bit instructions, but the binaries aren't huge.
>
Yeah, that is what n32 is for. You get more registers, but pointers are
still 32-bit. You still need a mips64 CHOST to build n32 binaries, however.
Steve
next prev parent reply other threads:[~2004-09-24 15:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 13:54 Kernel 2.6 for R4600 Indy Stuart Longland
2004-09-23 14:51 ` Ladislav Michl
2004-09-23 15:00 ` Stephen P. Becker
2004-09-24 0:16 ` Stuart Longland
2004-09-24 9:07 ` Florian Lohoff
2004-09-24 15:42 ` Stuart Longland
2004-09-24 16:44 ` Florian Lohoff
2004-09-24 13:05 ` Stephen P. Becker
2004-09-24 13:17 ` Robin Humble
2004-09-24 13:27 ` Stephen P. Becker
2004-09-24 13:43 ` Robin Humble
2004-09-24 15:13 ` Stephen P. Becker [this message]
2004-09-23 15:48 ` Florian Lohoff
2004-10-02 18:50 ` Thiemo Seufer
2004-10-02 20:40 ` Thiemo Seufer
2004-10-02 23:47 ` Thiemo Seufer
2004-10-03 0:58 ` Maciej W. Rozycki
2004-10-04 14:52 ` Ralf Baechle
2004-10-04 23:48 ` Maciej W. Rozycki
2004-10-05 19:04 ` Ralf Baechle
2004-10-05 19:35 ` Maciej W. Rozycki
2004-10-07 12:28 ` Ralf Baechle
2004-10-03 11:40 ` Thomas Bogendoerfer
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=4154398E.3070806@gentoo.org \
--to=geoman@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=rjh@cita.utoronto.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.