linux-mips
[Top] [All Lists]

Re: RFC: A new MIPS64 ABI

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: RFC: A new MIPS64 ABI
From: David Daney <ddaney@caviumnetworks.com>
Date: Mon, 09 May 2011 10:47:03 -0700
Cc: linux-mips <linux-mips@linux-mips.org>, GCC <gcc@gcc.gnu.org>, binutils <binutils@sourceware.org>, Prasun Kapoor <prasun.kapoor@caviumnetworks.com>, rdsandiford@googlemail.com
In-reply-to: <20110509142828.GA7196@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4D5990A4.2050308__41923.1521235362$1297715435$gmane$org@caviumnetworks.com> <87hbbxqihm.fsf@firetop.home> <20110509142828.GA7196@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10
On 05/09/2011 07:28 AM, Ralf Baechle wrote:
On Mon, Feb 21, 2011 at 07:45:41PM +0000, Richard Sandiford wrote:

David Daney<ddaney@caviumnetworks.com>  writes:
Background:

Current MIPS 32-bit ABIs (both o32 and n32) are restricted to 2GB of
user virtual memory space.  This is due the way MIPS32 memory space is
segmented.  Only the range from 0..2^31-1 is available.  Pointer
values are always sign extended.

Because there are not already enough MIPS ABIs, I present the ...

Proposal: A new ABI to support 4GB of address space with 32-bit
pointers.

FWIW, I'd be happy to see this go into GCC.

So am I for the kernel primarily because it's not really a new ABI but
an enhancement of the existing N32 ABI.


The patches are resting peacefully on my laptop. Now with endorcements like these, I may be forced to actually finish them...

David Daney

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