From: Matthias Klose <doko@ubuntu.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Andrew Haley <aph@redhat.com>, java-patches@gcc.gnu.org
Subject: Re: [PATCH] Enable java for aarch64
Date: Mon, 15 Apr 2013 07:31:00 -0000 [thread overview]
Message-ID: <516BACBF.6000000@ubuntu.com> (raw)
In-Reply-To: <mvmobdgw9sr.fsf@hawking.suse.de>
Am 15.04.2013 09:08, schrieb Andreas Schwab:
> Andrew Haley <aph@redhat.com> writes:
>
>> Looks basically OK. What were the failures, though?
>
> FAIL: TestClosureGC run
> FAIL: Array_3 execution - source compiled test
> FAIL: Array_3 -findirect-dispatch execution - source compiled test
> FAIL: Array_3 -O3 execution - source compiled test
> FAIL: Array_3 -O3 -findirect-dispatch execution - source compiled test
> FAIL: Invoke_1 execution - source compiled test
> FAIL: Invoke_1 -findirect-dispatch execution - source compiled test
> FAIL: Invoke_1 -O3 execution - source compiled test
> FAIL: Invoke_1 -O3 -findirect-dispatch execution - source compiled test
> FAIL: PR218 execution - source compiled test
> FAIL: PR218 -O3 execution - source compiled test
> FAIL: StackTrace2 execution - source compiled test
> FAIL: StackTrace2 -findirect-dispatch execution - source compiled test
> FAIL: StackTrace2 -O3 execution - source compiled test
> FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test
> FAIL: Throw_2 execution - source compiled test
> FAIL: Throw_2 -findirect-dispatch execution - source compiled test
> FAIL: Throw_2 -O3 execution - source compiled test
> FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test
> FAIL: Throw_3 execution - source compiled test
> FAIL: Throw_3 -findirect-dispatch execution - source compiled test
> FAIL: Throw_3 -O3 execution - source compiled test
> FAIL: Throw_3 -O3 -findirect-dispatch execution - source compiled test
> FAIL: pr83 -findirect-dispatch execution - source compiled test
> FAIL: pr83 -O3 -findirect-dispatch execution - source compiled test
> FAIL: sourcelocation output - source compiled test
> FAIL: sourcelocation -findirect-dispatch output - source compiled test
> FAIL: sourcelocation -O3 output - source compiled test
> FAIL: sourcelocation -O3 -findirect-dispatch output - source compiled test
does the interpreter and the byte code compilation work with these results?
Afaicr I did see the exact same set of test failures on other (Debian)
architectures in the past too.
Matthias
next prev parent reply other threads:[~2013-04-15 7:31 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 [this message]
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
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=516BACBF.6000000@ubuntu.com \
--to=doko@ubuntu.com \
--cc=aph@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).