From: Alan Modra <amodra@gmail.com>
To: Anthony Green <green@redhat.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
libffi-discuss@sourceware.org
Subject: Re: [RS6000] libffi little-endian
Date: Tue, 25 Jun 2013 00:11:00 -0000 [thread overview]
Message-ID: <20130625001110.GI21523@bubble.grove.modra.org> (raw)
In-Reply-To: <1796424869.21686355.1372086723737.JavaMail.root@redhat.com>
On Mon, Jun 24, 2013 at 11:12:03AM -0400, Anthony Green wrote:
> It's fine with me. Please commit it directly to GCC and I'll put it in the upstream.
Thanks! Committed revision 200383. (and 200384 to 4.8 branch.)
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2013-06-25 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130607013408.GI6878@bubble.grove.modra.org>
[not found] ` <CAGWvnynZsHaM+EaHQMOTiQKb6Pg5gT4OY8B1ZtwLEV+iGih7bw@mail.gmail.com>
2013-06-24 0:26 ` Alan Modra
2013-06-24 2:32 ` David Edelsohn
2013-06-24 15:12 ` Anthony Green
2013-06-25 0:11 ` Alan Modra [this message]
2013-06-07 10:28 Alan Modra
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=20130625001110.GI21523@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@redhat.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).