From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 57208@debbugs.gnu.org
Subject: bug#57208: 29.0.50; Uninitialized compilation warnings in xterm.c
Date: Mon, 15 Aug 2022 08:52:16 +0800 [thread overview]
Message-ID: <875yius4zj.fsf@yahoo.com> (raw)
In-Reply-To: <87bksmom16.fsf@tcd.ie> (Basil L. Contovounesios's message of "Sun, 14 Aug 2022 18:57:41 +0300")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> Severity: minor
> Tags: patch
>
> Compiling with GCC 12 and -Og, I get the following -Wmaybe-uninitialized
> warnings:
>
> xterm.c: In function ‘x_dnd_free_toplevels’:
> xterm.c:2918:17: warning: ‘dpy’ may be used uninitialized [-Wmaybe-uninitialized]
> 2918 | dpyinfo = x_display_info_for_display (dpy);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> xterm.c:2853:12: note: ‘dpy’ was declared here
> 2853 | Display *dpy;
> | ^~~
>
> xterm.c: In function ‘xm_setup_dnd_targets’:
> xterm.c:2284:21: warning: ‘recs’ may be used uninitialized [-Wmaybe-uninitialized]
> 2284 | recs[header.target_list_count - 1]->targets[i] = targets_sorted[i];
> | ^
> xterm.c:2112:26: note: ‘recs’ was declared here
> 2112 | xm_targets_table_rec **recs;
> | ^~~~
>
> They're bogus, right? Is it okay to silence them as follows?
Yes, those are all bogus. I installed something different to pacify
them on master.
Thanks.
next prev parent reply other threads:[~2022-08-15 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 15:57 bug#57208: 29.0.50; Uninitialized compilation warnings in xterm.c Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 0:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-15 20:34 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 2:36 ` Eli Zaretskii
2022-08-23 15:27 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yius4zj.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=57208@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).