This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 9.1 release 2019-12-23 update
- From: Tom Tromey <tom at tromey dot com>
- To: Andrew Burgess <andrew dot burgess at embecosm dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sourceware dot org
- Date: Fri, 03 Jan 2020 09:21:40 -0700
- Subject: Re: GDB 9.1 release 2019-12-23 update
- References: <20191223093031.GE11677@adacore.com> <835zi7xh7o.fsf@gnu.org> <20191224034652.GA25918@adacore.com> <20191224122354.GH3865@embecosm.com>
>>>>> "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