public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Andrew Haley <aph@redhat.com>
Cc: Matthias Klose <doko@ubuntu.com>, java-patches@gcc.gnu.org
Subject: Re: [PATCH] Enable java for aarch64
Date: Tue, 16 Apr 2013 07:45:00 -0000	[thread overview]
Message-ID: <mvm8v4ivryy.fsf@hawking.suse.de> (raw)
In-Reply-To: <516BC109.3060601@redhat.com> (Andrew Haley's message of "Mon, 15	Apr 2013 09:57:45 +0100")

Andrew Haley <aph@redhat.com> writes:

> 	slow_pthread_self=no
> 	can_unwind_signal=no
> 	CHECKREFSPEC=-fcheck-references
> 	DIVIDESPEC=-fuse-divide-subroutine

With these settings, I get the following results:

# of expected passes		2574
# of unexpected failures	8
# of untested testcases		4

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: 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

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2013-04-16  7:45 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 [this message]
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=mvm8v4ivryy.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=aph@redhat.com \
    --cc=doko@ubuntu.com \
    --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).