From: Andrew Pinski <pinskia@gmail.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
x32-abi@googlegroups.com, "H.J. Lu" <hjl.tools@gmail.com>,
GCC Development <gcc@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: x32 psABI draft version 0.2
Date: Wed, 16 Feb 2011 20:39:00 -0000 [thread overview]
Message-ID: <AANLkTimy7LaUE_pOOfE3ai37QEKhj_irNPacRq1dVBSP@mail.gmail.com> (raw)
In-Reply-To: <4D5C34F8.9060506@tilera.com>
On Wed, Feb 16, 2011 at 12:35 PM, Chris Metcalf <cmetcalf@tilera.com> wrote:
> For what it's worth, the Tilera 64-bit architecture (forthcoming) includes
> support for a 32-bit compatibility layer that is similar to x32. It uses
> 64-bit registers throughout (e.g. for double and long long), but 32-bit
> addresses. The addresses between 2GB and 4GB are not directly usable as
> 64-bit addresses since we sign-extend all 32-bit values to make the ISA
> more straightforward. We use the "compat" layer to provide our syscall
> table, since we don't have a traditional compatibility layer in this mode
> (unlike x86_64 and i386).
This sounds more like MIPS' n32 than x32 really.
-- Pinski
next prev parent reply other threads:[~2011-02-16 20:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 19:22 H.J. Lu
2011-02-16 20:04 ` H. Peter Anvin
2011-02-16 20:29 ` Roland McGrath
2011-02-16 20:35 ` Chris Metcalf
2011-02-16 20:39 ` Andrew Pinski [this message]
2011-02-16 20:46 ` H.J. Lu
2011-02-16 22:13 ` Chris Metcalf
2011-02-17 8:35 ` Jan Beulich
2011-02-17 12:14 ` H.J. Lu
2011-02-17 16:14 ` John Reiser
2011-02-17 17:59 ` Jakub Jelinek
2011-02-17 14:29 ` Jakub Jelinek
2011-02-17 15:22 ` Jan Hubicka
2011-02-17 15:30 ` H.J. Lu
2011-02-17 15:45 ` Jan Hubicka
2011-02-17 15:49 ` H.J. Lu
2011-02-17 16:10 ` Jan Beulich
2011-02-17 17:59 ` H.J. Lu
2011-02-18 8:10 ` Jan Beulich
2011-02-18 17:53 ` H.J. Lu
2011-02-18 20:32 ` Jan Hubicka
2011-02-21 8:04 ` Jan Beulich
2011-02-17 18:07 ` Jakub Jelinek
2011-02-17 19:56 ` H. Peter Anvin
2011-02-17 22:50 ` Jan Hubicka
2011-02-17 23:00 ` H. Peter Anvin
2011-02-17 23:07 ` Jakub Jelinek
2011-02-18 8:49 ` Jan Beulich
2011-02-17 18:14 ` Joseph S. Myers
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=AANLkTimy7LaUE_pOOfE3ai37QEKhj_irNPacRq1dVBSP@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=binutils@sourceware.org \
--cc=cmetcalf@tilera.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=x32-abi@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).