From: "H. Peter Anvin" <hpa@zytor.com>
To: x32-abi@googlegroups.com
Cc: Mark Butler <butlerm@middle.net>, "H.J. Lu" <hjl.tools@gmail.com>,
discuss@x86-64.org, GCC Development <gcc@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>,
GDB <gdb@sourceware.org>
Subject: Re: [x86-64 psABI] RFC: Extend x86-64 psABI to support x32
Date: Thu, 28 Jun 2012 21:06:00 -0000 [thread overview]
Message-ID: <4FECC71F.50207@zytor.com> (raw)
In-Reply-To: <af4adaed-508a-439f-92db-21d4385d316e@googlegroups.com>
On 06/28/2012 02:03 PM, Mark Butler wrote:
> On Tuesday, June 26, 2012 1:53:01 PM UTC-6, H. Peter Anvin wrote:
>
> It's worth noting that there are *no* Linux platforms that are not
> ILP32
> or LP64, so adding a third memory model is likely to cause even more
> problems...
>
>
> Care to comment on what sort of things would be likely to cause a large
> number of problems porting to an L64P32 model? I understand that L32P64
> (as in Windows 64 bit) causes lots of problems, because there is a lot
> of code that assumes that a pointer can be converted to a long and back.
> That would not be a problem with L64P32 however, because there
> pointers would be smaller than longs rather than larger.
Every time you introduce a new model you will have problems, but in
Linux it is a strong assumption that sizeof(long) == sizeof(void *).
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-06-28 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 17:31 H.J. Lu
2012-05-14 17:34 ` H. Peter Anvin
2012-05-14 17:44 ` H.J. Lu
2012-05-15 16:08 ` [discuss] " Michael Matz
2012-05-15 16:18 ` H.J. Lu
2012-05-17 19:50 ` H.J. Lu
[not found] ` <ccd4a6ab-f279-477f-b48b-94b8f4afd37d@googlegroups.com>
2012-06-26 19:48 ` H.J. Lu
2012-06-26 19:53 ` H. Peter Anvin
[not found] ` <af4adaed-508a-439f-92db-21d4385d316e@googlegroups.com>
2012-06-28 21:06 ` H. Peter Anvin [this message]
[not found] ` <69b1606d-6150-46eb-a426-93bfad19e7a2@googlegroups.com>
2012-06-26 21:23 ` H.J. Lu
[not found] ` <bde2af16-b04e-4e17-a22e-3fe0941e2496@googlegroups.com>
2012-06-27 12:02 ` H.J. Lu
2012-06-27 18:24 ` Magnus Fromreide
2012-06-27 18:29 ` H.J. Lu
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=4FECC71F.50207@zytor.com \
--to=hpa@zytor.com \
--cc=binutils@sourceware.org \
--cc=butlerm@middle.net \
--cc=discuss@x86-64.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.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).