From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
GCC Development <gcc@gcc.gnu.org>,
LKML <linux-kernel@vger.kernel.org>,
x32-abi@googlegroups.com
Subject: Re: X32 psABI status update
Date: Mon, 7 Mar 2011 16:33:06 -0500 [thread overview]
Message-ID: <201103071633.08197.vapier@gentoo.org> (raw)
In-Reply-To: <AANLkTik53Ss4hk3_nproctYLX0=imnt4HOt=pGV5idcU@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 476 bytes --]
On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
>
> https://sites.google.com/site/x32abi/
>
> The major remaining issues are glibc/gcc testsuite failures,
> kernel core dump and signal handler unwind.
are you getting a unique host tuple for this ? or are you extending x86_64-
linux-gnu ? so the only way of knowing which ABI is to check for the output
of the compiler+compiler flags ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-03-07 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 19:08 X32 psABI status update H.J. Lu
2011-03-06 17:28 ` H.J. Lu
2011-03-07 21:33 ` Mike Frysinger [this message]
2011-03-16 4:17 ` H.J. Lu
2011-03-16 4:30 ` Mike Frysinger
2011-03-16 4:51 ` H.J. Lu
2011-03-16 5:24 ` Mike Frysinger
2011-03-16 12:39 ` H.J. Lu
2011-03-17 2:57 ` Mike Frysinger
2011-03-17 5:21 ` H.J. Lu
2011-03-17 5:45 ` Mike Frysinger
2011-03-17 14:43 ` H.J. Lu
2011-03-17 17:38 ` Richard Henderson
2011-03-21 5:08 ` Mike Frysinger
2011-03-21 5:35 ` H.J. Lu
2011-03-21 5:53 ` Mike Frysinger
2011-03-21 6:54 ` H.J. Lu
2011-03-21 8:20 ` Michael Matz
2011-03-21 10:52 ` H.J. Lu
[not found] ` <201103160124.42939.vapier__14164.6524928094$1300277836$gmane$org@gentoo.org>
2011-03-16 12:39 ` Andreas Schwab
2011-03-16 4:19 ` H.J. Lu
2011-03-17 8:46 ` X32 syscall number base Mike Frysinger
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=201103071633.08197.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 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.