linux-mips
[Top] [All Lists]

Re: [OFF-TOPIC] Cobalt 64-bit, what for? (was: 64-bit fix)

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [OFF-TOPIC] Cobalt 64-bit, what for? (was: 64-bit fix)
From: Dominic Sweetman <dom@mips.com>
Date: Fri, 15 Apr 2005 11:18:08 +0100
Cc: Dominique Quatravaux <dom@kilimandjaro.dyndns.org>, Peter Horton <pdh@colonel-panic.org>, linux-mips@linux-mips.org
In-reply-to: <20050415101422.GB5414@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050414185949.GA5578@skeleton-jack> <425F8776.6080703@kilimandjaro.dyndns.org> <20050415101422.GB5414@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
Ralf Baechle (ralf@linux-mips.org) writes:

> > And doesn't 64 bit mode have costs of its own (doubled i-fetch bandwidth
> > for starters)?

64-bit MIPS CPUs still have 32-bit instructions... it's the registers
and addressing range which grow, not the instructions.

Program data segments tend to grow when you use 64-bit pointers (N64
does, but N32 - paradoxically still a 64-bit ABI - doesn't)

--
Dominic Sweetman
MIPS Technologies

<Prev in Thread] Current Thread [Next in Thread>