From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: luangruo@yahoo.com, 57208@debbugs.gnu.org
Subject: bug#57208: 29.0.50; Uninitialized compilation warnings in xterm.c
Date: Tue, 16 Aug 2022 05:36:31 +0300 [thread overview]
Message-ID: <838rnohq34.fsf@gnu.org> (raw)
In-Reply-To: <878rnp2qlw.fsf@tcd.ie> (bug-gnu-emacs@gnu.org)
> Cc: 57208@debbugs.gnu.org
> Date: Mon, 15 Aug 2022 23:34:19 +0300
> From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Po Lu [2022-08-15 08:52 +0800] wrote:
>
> > Yes, those are all bogus. I installed something different to pacify
> > them on master.
>
> Thanks. Just curious: what's the advantage of using UNINIT?
> When should it or shouldn't it be preferred?
It should be used when the warning is due to a compiler bug or
misfeature, and our code is fine. That's what UNINIT says: it says
that it's okay to leave this variable uninitialized.
next prev parent reply other threads:[~2022-08-16 2:36 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
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 [this message]
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=838rnohq34.fsf@gnu.org \
--to=eliz@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).