public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: java-patches@gcc.gnu.org,
		"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Enable java for aarch64
Date: Mon, 15 Apr 2013 07:10:00 -0000	[thread overview]
Message-ID: <CAFqB+PzuKmrCn_7gRRxM--zR_F6kd1mk+1NV7=uV0TU4V8jKAA@mail.gmail.com> (raw)
In-Reply-To: <516A905B.4020801@ubuntu.com>

Yvan's patch was checked in a few days ago...

/Marcus

r197770 | clyon | 2013-04-11 13:06:04 +0100 (Thu, 11 Apr 2013) | 12 lines

2013-03-16  Yvan Roux <yvan.roux@linaro.org>

        * include/private/gcconfig.h (AARCH64): New macro (defined only if
        __aarch64__).
        * include/private/gcconfig.h (mach_type_known):
        Update comment adding ARM AArch64 target.
        * include/private/gcconfig.h (NOSYS, mach_type_known,CPP_WORDSZ,
        MACH_TYPE, ALIGNMENT, HBLKSIZE, OS_TYPE, LINUX_STACKBOTTOM,
        USE_GENERIC_PUSH_REGS, DYNAMIC_LOADING, DATASTART, DATAEND,
        STACKBOTTOM): Define for AArch64.

On 14 April 2013 12:17, Matthias Klose <doko@ubuntu.com> wrote:
> Am 13.04.2013 20:21, schrieb Andreas Schwab:
>> This enables building java for aarch64.
>
> Afaics, the aarch64 changes for boehm-gc are not yet checked in. Aren't these
> needed as a prerequisite?
>

      reply	other threads:[~2013-04-15  7:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 18:21 Andreas Schwab
2013-04-14 10:58 ` Andrew Haley
2013-04-15  7:08   ` Andreas Schwab
2013-04-15  7:31     ` Matthias Klose
2013-04-15  8:19       ` Andreas Schwab
2013-04-15  8:57         ` Andrew Haley
2013-04-16  7:45           ` Andreas Schwab
2013-04-16  8:13             ` Andrew Haley
2013-04-14 11:17 ` Matthias Klose
2013-04-15  7:10   ` Marcus Shawcroft [this message]

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='CAFqB+PzuKmrCn_7gRRxM--zR_F6kd1mk+1NV7=uV0TU4V8jKAA@mail.gmail.com' \
    --to=marcus.shawcroft@gmail.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.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).