From: Jerry DeLisle <jvdelisle@charter.net>
To: John David Anglin <dave.anglin@bell.net>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, fortran@gcc.gnu.org
Subject: Re: [PATCH] Fix failure of gfortran.dg/backtrace_1.f90 on hppa*-*-hpux*
Date: Sat, 23 Jan 2016 23:12:00 -0000 [thread overview]
Message-ID: <56A408F3.4000806@charter.net> (raw)
In-Reply-To: <C194690B-6CF6-476E-986C-4EC1A4B5A953@bell.net>
On 01/23/2016 02:40 PM, John David Anglin wrote:
> Ping.
>
> On 2015-12-28, at 2:58 PM, John David Anglin wrote:
>
>> The hppa*-*-hpux* target does not support __sync builtins. As a result, libbacktrace does not
>> support backtraces when threads are active.
>>
>> Instead of always assuming threads are active in libgfortran/runtime/backtrace.c, the attached
>> patch uses __gthread_active_p() to determine whether threads are active or not. In addition,
>> if backtrace_create_state returns NULL, we just return from show_backtrace(). This avoids a
>> segmentation fault when threads are active.
>>
>> This fixes the failure of gfortran.dg/backtrace_1.f90 on hpux.
>>
>> Tested on hppa2.0w-hp-hpux11.11 and hppa64-hp-hpux11.11.
>>
>> Okay for trunk?
>>
OK,
Jerry
prev parent reply other threads:[~2016-01-23 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 19:58 John David Anglin
2016-01-23 22:40 ` John David Anglin
2016-01-23 23:12 ` Jerry DeLisle [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=56A408F3.4000806@charter.net \
--to=jvdelisle@charter.net \
--cc=dave.anglin@bell.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-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).