From: Andrew Haley <aph@redhat.com>
To: Chen Gang <gang.chen.5i5j@gmail.com>, Mike Stump <mikestump@comcast.net>
Cc: Michael Eager <eager@eagerm.com>, Jeff Law <law@redhat.com>,
davem@redhat.com,
gcc-patches List <gcc-patches@gcc.gnu.org>,
java-patches@gcc.gnu.org
Subject: Libjava test failure Was: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'
Date: Mon, 06 Oct 2014 08:37:00 -0000 [thread overview]
Message-ID: <543254DB.9020600@redhat.com> (raw)
In-Reply-To: <543215AE.7080206@gmail.com>
On 06/10/14 05:08, Chen Gang wrote:
> After try normal configure, get almost the same result, I guess, our
> testsuite under Darwin x86_64 is OK.
>
> If no any additional reply within a week, I shall continue to try to
> analyze the libjava Throw_2 issue.
Throw_2 is a test specially contrived to detect segfaults that are
not being correctly detected and turned into NullPointerException()s.
A failure indicates that the segfault signal handler is broken.
Andrew.
next prev parent reply other threads:[~2014-10-06 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bekwguasixaphab5pghrhbxp.1411603920412@email.android.com>
2014-10-05 3:10 ` Chen Gang
2014-10-05 3:26 ` Chen Gang
2014-10-06 4:03 ` Chen Gang
2014-10-06 8:37 ` Andrew Haley [this message]
2014-10-06 13:48 ` Libjava test failure Was: " Chen Gang
2014-10-06 13:54 ` Andrew Haley
2014-10-06 14:21 ` Chen Gang
2014-10-06 14:30 ` Andrew Haley
2014-10-06 14:54 ` Chen Gang
2014-10-06 15:00 ` Andrew Haley
2014-10-06 15:30 ` Chen Gang
2014-10-06 17:29 ` Mike Stump
2014-10-06 23:12 ` Chen Gang
2014-10-06 23:41 ` Chen Gang
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=543254DB.9020600@redhat.com \
--to=aph@redhat.com \
--cc=davem@redhat.com \
--cc=eager@eagerm.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mikestump@comcast.net \
/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).