From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Andrew Haley <aph@redhat.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: Re: 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 14:21:00 -0000 [thread overview]
Message-ID: <5432A6C5.8040205@gmail.com> (raw)
In-Reply-To: <54329F17.7050107@redhat.com>
On 10/6/14 21:54, Andrew Haley wrote:
> On 10/06/2014 02:53 PM, Chen Gang wrote:
>> On 10/6/14 16:37, Andrew Haley wrote:
>>> 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.
>>
>> OK, thank, at present, it passes compiling (can generate 'Throw_2.exe'),
>> and after run it without any parameters, "1" is printed, but "2" is not
>> printed.
>>
>> Under Fedora 20 x86_64, the same gcc code, it is OK ("2" can be printed),
>> but under Darwin x86_64, it is "Abort trap: 6" instead of. The related
>> code: "try{Double.parseDouble(str());}catch", and "str(){return null;}".
>>
>> And I shall continue to try to analyze it (within this month), and
>> welcome any additional ideas, suggestions, and completion for it,
>
> Not every platform supports unwinding through signal handlers. In x86
> Linux there is some very clever code which interacts with the kernel to
> allow this.
>
Excuse me, I am not quite familiar with Java, I guess what you said is:
- The related feature need OS kernel support, if OS kernel does not
support, it may report "Abort trap: 6" or others.
- And OS kernel has feature to support "1" printed does not mean it
also has feature to support "2" printed.
- And I need try to make sure that my current Darwin kernel whether
supports it or not.
If what I guess is incorrect, please let me know, thanks.
For me, whether Darwin kernel supports or not, we have to improve
current implementation (may be testsuite configure or Makefile) to
avoid testsuite breaking.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-10-06 14:21 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 ` Libjava test failure Was: " Andrew Haley
2014-10-06 13:48 ` Chen Gang
2014-10-06 13:54 ` Andrew Haley
2014-10-06 14:21 ` Chen Gang [this message]
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=5432A6C5.8040205@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=aph@redhat.com \
--cc=davem@redhat.com \
--cc=eager@eagerm.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).