From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Subject: Re: -Wall
Date: Mon, 4 Apr 2016 11:51:53 -0700 [thread overview]
Message-ID: <5702B7C9.6010805@cs.ucla.edu> (raw)
In-Reply-To: <m3inzxnsif.fsf@gnus.org>
On 04/04/2016 11:22 AM, Lars Magne Ingebrigtsen wrote:
> There's a lot fewer warnings when compiling with -Wall in emacs/src now
> than there used to be, but there should be none, I think.
I'm getting no warnings when I build.
> Are there any of them that, like, are there for a reason (i.e., we
> disagree with the gcc people that those things should be warned about),
> or are they all things that should be fixed?
>
It's more the other way around: -Wall doesn't generate enough warnings.
Please try './configure --enable-gcc-warnings'. This uses -Wall plus
some other warning flags that are useful in practice. I regularly check
that this builds cleanly for recent GCC on my platform (Fedora 23, GCC
5.3.1 20151207 (Red Hat 5.3.1-2)), and occasionally for recent Ubuntu,
both using default configure-time options.
If you'd like to take up the burden of porting --enable-gcc-warnings to
other platforms feel free, though my suggestion is to not bother with
older and/or rarely-used platforms as they have too many bugs in this area.
next prev parent reply other threads:[~2016-04-04 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:22 -Wall Lars Magne Ingebrigtsen
2016-04-04 18:51 ` Paul Eggert [this message]
2016-04-04 18:58 ` -Wall Lars Magne Ingebrigtsen
2016-04-05 0:20 ` -Wall Paul Eggert
2016-04-05 7:39 ` -Wall Lars Magne Ingebrigtsen
2016-04-05 14:35 ` -Wall Eli Zaretskii
2016-04-05 15:12 ` -Wall Paul Eggert
2016-04-06 11:49 ` -Wall Lars Magne Ingebrigtsen
2016-04-06 12:02 ` -Wall Stefan Monnier
2016-04-07 5:16 ` -Wall Paul Eggert
2016-04-04 23:22 ` -Wall John Wiegley
2016-04-05 13:16 ` -Wall Philipp Stephani
2016-04-05 14:46 ` -Wall Eli Zaretskii
2016-04-05 15:09 ` -Wall John Wiegley
2016-04-05 14:54 ` -Wall Richard Stallman
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=5702B7C9.6010805@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).