public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Anthony Green <green@moxielogic.com>
Cc: GCJ-patches <java-patches@gcc.gnu.org>,
	 Marcus Shawcroft <marcus.shawcroft@arm.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: please merge libffi trunk into GCC
Date: Mon, 10 Dec 2012 16:25:00 -0000	[thread overview]
Message-ID: <50C60CFF.50408@ubuntu.com> (raw)

Hi,

please could you merge libffi into GCC trunk for one more time? Motivation is to
get the aarch64 port into GCC 4.8. I assume such a merge would require approval
by the java maintainers. As an alternative, could the aarch64 port go to the
trunk even without a libffi merge?

I would like to see the aarch64 port in the gcc-4.7 aarch64 branch too.

Thanks, Matthias

             reply	other threads:[~2012-12-10 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 16:25 Matthias Klose [this message]
2012-12-10 16:51 ` Andrew Haley
2012-12-19 12:01   ` Anthony Green

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=50C60CFF.50408@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=green@moxielogic.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=marcus.shawcroft@arm.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).