From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release 2019-12-23 update
Date: Fri, 03 Jan 2020 16:21:00 -0000 [thread overview]
Message-ID: <877e28v7cb.fsf@tromey.com> (raw)
In-Reply-To: <20191224122354.GH3865@embecosm.com> (Andrew Burgess's message of "Tue, 24 Dec 2019 12:23:54 +0000")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> That said, I had a look at the code in question and I suspect the
Andrew> warning is incorrect, unless I'm missing some clever C++ corner case,
Andrew> which is quite possible. So, we have one of these:
Andrew> gdb::optional<ui_out_emit_list> asm_list;
Andrew> The "uninitialised" variable is a member of the ui_out_emit_list,
Andrew> being used during its destructor. But the destructor is only called
Andrew> if the ui_out_emit_list is initialised, which requires the member
Andrew> variable to be set....
Andrew> Currently I would be happy to release with the warning present.
You didn't miss anything. This is just a bug in gcc (IMO).
There's a discussion here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
Tom
next prev parent reply other threads:[~2020-01-03 16:21 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
2020-01-03 16:21 ` Tom Tromey [this message]
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=877e28v7cb.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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