From: David Edelsohn <dje.gcc@gmail.com>
To: FX <fxcoudert@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>,
Janne Blomqvist <blomqvist.janne@gmail.com>,
Ian Lance Taylor <ian@airs.com>
Subject: Re: [PATCH, fortran] PR 53379 Backtrace on error termination
Date: Tue, 08 Sep 2015 13:43:00 -0000 [thread overview]
Message-ID: <CAGWvny==F7BJ3SfiJQzaUcL3E0nvjOSe+LmRSkLYyhBUc_Lcsg@mail.gmail.com> (raw)
In-Reply-To: <5474EA6F-E6C0-4FA0-B299-C0D9558D6ACB@gmail.com>
On Tue, Sep 8, 2015 at 9:15 AM, FX <fxcoudert@gmail.com> wrote:
>> libbacktrace is not supported on AIX. This patch breaks bootstrap on AIX.
>> It's okay if Fortran backtrace does not work on AIX, but not all
>> targets support libbacktrace.
>
> libbacktrace is designed to be compiled on all targets. Some targets offer full support, some offer nothing, but libbacktrace is compiled and its headers provided in all cases.
>
> Can you please give us something to investigate? Like, the error message you’re seeing.
/home/dje/src/src/libbacktrace/posix.c: In function 'backtrace_open':
/home/dje/src/src/libbacktrace/posix.c:67:32: error: overflow in
implicit constant conversion [-Werror=overflow]
descriptor = open (filename, O_RDONLY | O_BINARY | O_CLOEXEC);
^
Thanks, David
next prev parent reply other threads:[~2015-09-08 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 12:30 David Edelsohn
2015-09-08 13:22 ` FX
2015-09-08 13:43 ` David Edelsohn [this message]
2015-09-08 13:49 ` David Edelsohn
2015-09-08 13:53 ` FX
2015-09-08 14:00 ` David Edelsohn
2015-09-08 15:36 ` Mike Stump
2015-09-08 16:46 ` FX
2015-09-09 4:41 ` Ian Lance Taylor
2015-09-09 13:00 ` David Edelsohn
2015-09-09 15:09 ` Mike Stump
2015-09-17 14:19 ` David Edelsohn
2015-09-17 15:06 ` Ian Lance Taylor
2015-09-08 13:52 ` FX
-- strict thread matches above, loose matches on Subject: below --
2015-09-04 22:10 Janne Blomqvist
2015-09-04 22:52 ` 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='CAGWvny==F7BJ3SfiJQzaUcL3E0nvjOSe+LmRSkLYyhBUc_Lcsg@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.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).