From: Ian Lance Taylor <iant@google.com>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [patch,libgfortran,toplevel] Use libbacktrace in libgfortran
Date: Fri, 14 Aug 2015 14:19:00 -0000 [thread overview]
Message-ID: <CAKOQZ8ybTGCgs9ff0=OBXf0Dwr-MYygG4tD2fwwO9iTZ3JAq7w@mail.gmail.com> (raw)
In-Reply-To: <16C6D412-891E-41D7-A250-6EE06002AEBB@gmail.com>
On Fri, Aug 14, 2015 at 1:32 AM, 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)
This change (and the corresponding change to Makefile.in) is OK.
Thanks.
Ian
next prev parent reply other threads:[~2015-08-14 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 9:23 FX
2015-08-14 14:19 ` Ian Lance Taylor [this message]
2015-08-24 12:27 ` Build break on SPU (and other non-mmap systems?) (Re: [patch,libgfortran,toplevel] Use libbacktrace in libgfortran) Ulrich Weigand
2015-08-24 12:41 ` FX
2015-08-24 13:15 ` Ulrich Weigand
2015-08-24 13:44 ` FX
2015-08-24 17:31 ` Jeff Law
2015-08-24 18:56 ` Ulrich Weigand
2015-08-14 13:19 [patch,libgfortran,toplevel] Use libbacktrace in libgfortran Uros Bizjak
2015-08-14 14:31 ` FX
2015-08-23 20:14 ` Janne Blomqvist
2015-08-23 20:59 ` FX
2015-08-23 21:27 ` Janne Blomqvist
2015-08-24 7:15 ` FX
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='CAKOQZ8ybTGCgs9ff0=OBXf0Dwr-MYygG4tD2fwwO9iTZ3JAq7w@mail.gmail.com' \
--to=iant@google.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--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).