From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: FX <fxcoudert@gmail.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [patch,libgfortran,toplevel] Use libbacktrace in libgfortran
Date: Sun, 23 Aug 2015 20:14:00 -0000 [thread overview]
Message-ID: <CAO9iq9GB+4pDgn+g=kwfpT_zKLugHAX9qVSopUu=5NjLP93XJw@mail.gmail.com> (raw)
In-Reply-To: <DED6598E-A106-4BBE-9943-575D1489FECF@gmail.com>
On Fri, Aug 14, 2015 at 5:18 PM, FX <fxcoudert@gmail.com> wrote:
>>> Use libbacktrace (instead of our own unwind-based code) to display backtraces from libgfortran
>>> upon error or user request.
>>>
>>> 1. In toplevel Makefile.def, make libgfortran depend on libbacktrace (needs global reviewer
>>> approval)
>>> 2. In gcc/fortran/config-lang.in, add libbacktrace to target_libs
>>> 3. In libgfortran, we remove our own code and substitute calls to libbacktrace
>>>
>>> Bootstrapped and regtested on x86_64-pc-linux-gnu (which has full libbacktrace support) and
>>> x86_64-apple-darwin14 (which has minimal libbacktrace support). OK to commit to trunk?
>>
>> backtrace.ChangeLog is unreadable for me …
>
> Sending again, this time with .txt extension, hoping this makes it go through OK.
Awesome! Looks good. I only have one small bikeshed request: Can you
make the output format match the existing code?
(As there seems to be no GNU (or otherwise) standard how backtraces
should look, in order to minimize user confusion I made the current
code produce output matching gdb backtraces as close as seemed
reasonable.)
Ok with that change.
--
Janne Blomqvist
next prev parent reply other threads:[~2015-08-23 19:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 13:19 Uros Bizjak
2015-08-14 14:31 ` FX
2015-08-23 20:14 ` Janne Blomqvist [this message]
2015-08-23 20:59 ` FX
2015-08-23 21:27 ` Janne Blomqvist
2015-08-24 7:15 ` FX
2015-08-24 16:00 ` Fix libbacktrace -fPIC breakage from "Use libbacktrace in libgfortran" Hans-Peter Nilsson
2015-08-24 16:08 ` FX
2015-08-24 16:44 ` Hans-Peter Nilsson
2015-08-24 18:42 ` FX
2015-08-25 3:29 ` Ian Lance Taylor
2015-08-25 13:25 ` Ulrich Weigand
2015-08-25 17:09 ` Hans-Peter Nilsson
2015-08-25 17:57 ` Ulrich Weigand
2015-08-26 0:09 ` Hans-Peter Nilsson
2015-08-26 12:17 ` Ulrich Weigand
2015-08-26 12:34 ` Hans-Peter Nilsson
2015-08-26 15:37 ` [PATCH] Fix and simplify (Re: Fix libbacktrace -fPIC breakage from "Use libbacktrace in libgfortran") Ulrich Weigand
2015-08-27 4:02 ` Ian Lance Taylor
2015-08-27 13:38 ` Ulrich Weigand
2015-08-27 14:02 ` Ian Lance Taylor
2015-08-24 16:04 ` Fix libbacktrace -fPIC breakage from "Use libbacktrace in libgfortran" Hans-Peter Nilsson
-- strict thread matches above, loose matches on Subject: below --
2015-08-14 9:23 [patch,libgfortran,toplevel] Use libbacktrace in libgfortran FX
2015-08-14 14:19 ` Ian Lance Taylor
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='CAO9iq9GB+4pDgn+g=kwfpT_zKLugHAX9qVSopUu=5NjLP93XJw@mail.gmail.com' \
--to=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.com \
/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).