From: Florian Weimer <fw@deneb.enyo.de>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
LKML <linux-kernel@vger.kernel.org>,
x32-abi@googlegroups.com
Subject: Re: X32 psABI status
Date: Sat, 12 Feb 2011 22:10:52 +0100 [thread overview]
Message-ID: <87aai1gdr7.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <AANLkTikgfv+L9WS4s6n5mQcXWTzc6YMNUSsgBiAOmKbE@mail.gmail.com> (H. J. Lu's message of "Sat, 12 Feb 2011 11:41:01 -0800")
* H. J. Lu:
> We made lots of progresses on x32 pABI:
>
> https://sites.google.com/site/x32abi/
>
> 1. Kernel interface with syscall is close to be finalized.
> 2. GCC x32 branch is stabilizing.
> 3. The Bionic C library works with the syscall kernel interface.
>
> The next major milestone will be x32 glibc port.
It is a bit difficult to extract useful information from these
resources.
Is off_t 32 bits? Why is the ia32 compatiblity kernel interface used?
I'm sure a lot of people want to get rid of that in cases where they
control the whole software stack.
Is stack alignment to 16 bytes beneficial for X32?
next prev parent reply other threads:[~2011-02-12 21:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 19:41 X32 psABI status H.J. Lu
2011-02-12 21:10 ` Florian Weimer [this message]
2011-02-12 21:29 ` H.J. Lu
2011-02-12 23:04 ` H. Peter Anvin
2011-02-13 3:02 ` Andrew Pinski
2011-02-13 8:48 ` Florian Weimer
2011-02-13 13:45 ` H.J. Lu
2011-02-13 15:07 ` Florian Weimer
2011-02-13 15:13 ` H.J. Lu
2011-02-13 15:21 ` Florian Weimer
2011-02-13 15:37 ` H.J. Lu
2011-02-13 16:35 ` Petr Baudis
2011-02-13 16:48 ` H.J. Lu
2011-02-13 17:37 ` Joseph S. Myers
2011-02-13 15:43 ` Maciej W. Rozycki
2011-02-13 15:57 ` H.J. Lu
2011-02-13 20:10 ` Arnd Bergmann
2011-02-13 21:10 ` H.J. Lu
2011-02-13 21:16 ` H. Peter Anvin
2011-02-13 21:28 ` H.J. Lu
2011-02-13 22:03 ` H. Peter Anvin
2011-02-13 22:12 ` H.J. Lu
2011-02-13 21:33 ` Alan Cox
2011-02-14 1:52 ` H. Peter Anvin
2011-02-13 22:27 ` H. Peter Anvin
2011-02-13 22:28 ` Arnd Bergmann
2011-02-13 22:46 ` H. Peter Anvin
2011-02-13 22:57 ` Arnd Bergmann
2011-02-13 23:03 ` H.J. Lu
2011-02-13 23:39 ` Alan Cox
2011-02-13 23:50 ` H.J. Lu
2011-02-14 1:59 ` H. Peter Anvin
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=87aai1gdr7.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.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