GNU bug report logs - #57208
29.0.50; Uninitialized compilation warnings in xterm.c

Previous Next

Package: emacs;

Reported by: "Basil L. Contovounesios" <contovob <at> tcd.ie>

Date: Sun, 14 Aug 2022 15:58:02 UTC

Severity: minor

Tags: moreinfo, patch

Found in version 29.0.50

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>
Cc: luangruo <at> yahoo.com, 57208 <at> debbugs.gnu.org
Subject: bug#57208: 29.0.50; Uninitialized compilation warnings in xterm.c
Date: Tue, 16 Aug 2022 05:36:31 +0300

> Cc: 57208 <at> 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 <at> 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.
This bug report was last modified 2 years and 274 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.