From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release 2019-12-23 update
Date: Tue, 24 Dec 2019 15:52:00 -0000 [thread overview]
Message-ID: <834kxpwwje.fsf@gnu.org> (raw)
In-Reply-To: <20191224122354.GH3865@embecosm.com> (message from Andrew Burgess on Tue, 24 Dec 2019 12:23:54 +0000)
> Date: Tue, 24 Dec 2019 12:23:54 +0000
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>
> > > What about the compilation warning in record-btrace.c I reported in
> > > https://sourceware.org/ml/gdb-patches/2019-12/msg00706.html? Do we
> > > want to fix it?
> >
> > We can, but (IMO) not super critical. FWIW, I don't get the warning
> > when buidling on GNU/Linux.
>
> I can reproduce the warning on GNU/Linux, but it only crops up at some
> optimisation levels, -O0 doesn't warn for me, while -O1 and -O2 do.
> I've tested with GCC 8.3, 9.2, and a 10.??. This is all on a Fedora
> 27 system (yes, I really should update).
FTR, my GCC version is 8.3, and I did use -O2 optimizations.
Thanks.
next prev parent reply other threads:[~2019-12-24 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 9:30 Joel Brobecker
2019-12-23 14:14 ` Eli Zaretskii
2019-12-23 14:32 ` Eli Zaretskii
2019-12-24 3:47 ` Joel Brobecker
2019-12-24 12:24 ` Andrew Burgess
2019-12-24 15:52 ` Eli Zaretskii [this message]
2020-01-03 16:21 ` Tom Tromey
2019-12-24 16:21 ` Eli Zaretskii
2019-12-26 22:40 ` Christian Biesinger via gdb-patches
2019-12-27 7:49 ` Eli Zaretskii
2019-12-25 21:36 ` Andrew Burgess
2020-01-02 10:56 ` Joel Brobecker
2020-01-06 22:00 ` Andrew Burgess
2019-12-28 16:22 ` Hannes Domani via gdb-patches
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=834kxpwwje.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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