From: Paul Eggert <eggert@cs.ucla.edu>
To: Ken Brown <kbrown@cornell.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: 23640@debbugs.gnu.org, Andy Moreton <andrewjmoreton@gmail.com>
Subject: bug#23640: 25.1.50; Getting rid of compiler warnings
Date: Mon, 30 May 2016 16:29:15 -0700 [thread overview]
Message-ID: <574CCCCB.7000209@cs.ucla.edu> (raw)
In-Reply-To: <b5f88f09-1413-8853-bb41-a5ee3d00d810@cornell.edu>
Ken Brown wrote:
> Why not just unconditionally initialize the variables that gcc complains about?
That could make the code harder to understand. Someone who sees "int i = 0;" can
reasonably infer that the 0 is needed, i.e., that a later part of the code needs
the 0. Someone who sees "int i IF_LINT (= 0);" should be under no such illusion.
The tradition of hijacking the symbol 'lint' for GCC purposes has been used for
many years in several GNU packages. As the problem you mention affects only
optionally-generated warnings on non-GNU platforms, I suspect nobody has cared
until now about the issue. Anyway, I changed Emacs master to use the symbol
GCC_LINT instead; this should avoid the collision in names. Please give it a try.
The FreeBSD and Cygwin uses of 'lint' violate the C Standard. For example:
#define lint 1
#include <stdio.h>
_Noreturn int x;
This program violates a constraint so the C Standard requires a compile-time
diagnostic, but from what you say on FreeBSD and Cygwin the compiler misbehaves
and silently ignores the _Noreturn. I see that HBBroeker is independently making
a similar point on the Cygwin mailing list
<https://www.cygwin.com/ml/cygwin/2016-05/msg00405.html>.
next prev parent reply other threads:[~2016-05-30 23:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 18:40 bug#23640: 25.1.50; Getting rid of compiler warnings Ken Brown
2016-05-28 18:57 ` Eli Zaretskii
2016-05-28 21:47 ` Ken Brown
2016-05-29 22:43 ` Ken Brown
2016-05-30 11:39 ` Ken Brown
2016-05-30 14:41 ` Ken Brown
2016-05-30 16:20 ` Ken Brown
2016-05-30 23:29 ` Paul Eggert [this message]
2016-05-31 0:11 ` Ken Brown
2016-05-31 8:03 ` Andy Moreton
2016-05-31 22:22 ` Richard Stallman
2016-05-31 0:15 ` Paul Eggert
2016-06-01 8:35 ` Paul Eggert
2016-06-01 20:37 ` Richard Stallman
2016-06-01 21:10 ` Paul Eggert
2016-06-02 12:05 ` Andy Moreton
2016-06-03 3:35 ` Richard Stallman
2016-06-06 14:45 ` Paul Eggert
2016-06-07 6:19 ` Richard Stallman
2016-06-07 7:15 ` Paul Eggert
2016-06-08 4:00 ` Richard Stallman
2016-06-08 7:18 ` Paul Eggert
2016-06-08 17:06 ` Richard Stallman
2016-06-01 8:55 ` Paul Eggert
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=574CCCCB.7000209@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23640@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=eliz@gnu.org \
--cc=kbrown@cornell.edu \
/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).