From: Richard Henderson <rth@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Anthony Green <green@moxielogic.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
libffi-discuss@sourceware.org
Subject: Re: libffi is broken for x32
Date: Tue, 13 Jan 2015 01:13:00 -0000 [thread overview]
Message-ID: <54B47138.1090307@redhat.com> (raw)
In-Reply-To: <CAMe9rOpWdSeCvxRWiiwYbA7R7dNqtReFig=7vYJREzEBO6dD+w@mail.gmail.com>
On 01/12/2015 04:57 PM, H.J. Lu wrote:
> The problem is my x86_64-*-linux-gnux32 patch
>
> https://gcc.gnu.org/ml/gcc-patches/2012-08/msg01083.html
>
> was never accepted upstream. Can I apply it to config.guess
> in GCC?
Ah. Hmm. Perhaps the configure.host patch would be better after all.
r~
next prev parent reply other threads:[~2015-01-13 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMe9rOpTqX-d+CoSnxqug__gYv1HVZ8+6-KBqQ8fWo9+sH07Cg@mail.gmail.com>
2015-01-12 23:46 ` H.J. Lu
2015-01-13 0:29 ` Richard Henderson
2015-01-13 0:57 ` H.J. Lu
2015-01-13 1:13 ` Richard Henderson [this message]
2015-01-13 15:35 ` H.J. Lu
2015-01-13 15:51 ` Richard Henderson
2015-01-13 0:59 ` 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=54B47138.1090307@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@moxielogic.com \
--cc=hjl.tools@gmail.com \
--cc=libffi-discuss@sourceware.org \
/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).