From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>
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
Subject: Re: RFC: A new MIPS64 ABI
Date: Mon, 09 May 2011 10:47:03 -0700 [thread overview]
Message-ID: <4DC82897.7020206@caviumnetworks.com> (raw)
In-Reply-To: <20110509142828.GA7196@linux-mips.org>
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
next prev parent reply other threads:[~2011-05-09 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D5990A4.2050308__41923.1521235362$1297715435$gmane$org@caviumnetworks.com>
2011-02-21 19:45 ` RFC: A new MIPS64 ABI Richard Sandiford
2011-05-09 14:28 ` Ralf Baechle
2011-05-09 17:47 ` David Daney [this message]
2011-02-14 20:29 David Daney
2011-02-15 17:56 ` Alexandre Oliva
2011-02-15 18:08 ` David Daney
2011-05-06 8:29 ` Alexandre Oliva
2011-05-06 17:00 ` David Daney
2011-02-18 1:02 ` David Daney
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=4DC82897.7020206@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-mips@linux-mips.org \
--cc=prasun.kapoor@caviumnetworks.com \
--cc=ralf@linux-mips.org \
--cc=rdsandiford@googlemail.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.