All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: MIPS64 status?
Date: Mon, 14 Jan 2002 15:05:54 -0800	[thread overview]
Message-ID: <20020114150554.A29242@dea.linux-mips.net> (raw)
In-Reply-To: <20020113211323.A7115@momenco.com>; from mdharm@momenco.com on Sun, Jan 13, 2002 at 09:13:23PM -0800

On Sun, Jan 13, 2002 at 09:13:23PM -0800, Matthew Dharm wrote:

> As I understand it, 64-bit support is really two different things:  64-bit
> data path (i.e. unsigned long long) and 64-bit addressing (for more than 4G
> of RAM).

Right but due to the CPU architecture of pre-MIPS64 CPUs they always come
together unless the software does funny attempts at truncating OS support
to just 32-bit.  So the 32-bit kernel gives you none of the two, the mips64
kernel both.

> My understanding is that "MIPS64" generally refers to a kernel which
> supports a 64-bit data path, but we're still limited to 32-bit addressing.
> Is that correct?

MIPS64 is MIPS's MIPS64 processor architecture, mips64 is the 64-bit kernel.
That may sound like nitpicking but it's important to understand that both
are not the same.

> I suspect that this is very much a toolchain issue, as I don't think gcc
> will generate 64-bit addressing code.

Gcc is fine; the problem are binutils, that is as and ld.  As a result of
the gcc problems we don't have a 64-bit userspace either so all software
running on 64-bit kernels is currently old 32-bit software running in
compatibility mode.

  Ralf

  parent reply	other threads:[~2002-01-15  0:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14  5:13 MIPS64 status? Matthew Dharm
2002-01-14  8:13 ` Jason Gunthorpe
2002-01-14 20:00   ` Matthew Dharm
2002-01-14 20:00     ` Matthew Dharm
2002-01-14 20:42     ` Jason Gunthorpe
2002-01-14 23:07       ` Ralf Baechle
2002-01-15  0:08         ` Jason Gunthorpe
2002-01-15 20:59           ` Ralf Baechle
2002-01-15 20:00         ` John Heil
2002-01-15 20:55           ` Ralf Baechle
2002-01-16 18:55           ` Dominic Sweetman
2002-01-14 21:17     ` Dominic Sweetman
2002-01-14 21:17       ` Dominic Sweetman
2002-01-14 23:09       ` Ralf Baechle
2002-01-14 11:17 ` Dominic Sweetman
2002-01-14 12:54   ` Kevin D. Kissell
2002-01-14 12:54     ` Kevin D. Kissell
2002-01-14 13:37     ` Maciej W. Rozycki
2002-01-14 23:23     ` Ralf Baechle
2002-01-15 13:07       ` Maciej W. Rozycki
2002-01-14 23:22   ` Ralf Baechle
2002-01-15 19:11   ` Thiemo Seufer
2002-01-14 23:05 ` Ralf Baechle [this message]
2002-01-14 23:25   ` Matthew Dharm
2002-01-14 23:25     ` Matthew Dharm
2002-01-14 23:45     ` Ralf Baechle
2002-01-14 23:59     ` Jason Gunthorpe
2002-01-15  0:27       ` Matthew Dharm
2002-01-15  0:27         ` Matthew Dharm

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=20020114150554.A29242@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.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 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.