From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: -Wall
Date: Tue, 5 Apr 2016 08:12:50 -0700 [thread overview]
Message-ID: <5703D5F2.4000708@cs.ucla.edu> (raw)
In-Reply-To: <m3oa9o4i95.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On 04/05/2016 12:39 AM, Lars Magne Ingebrigtsen wrote:
> warnings should be enabled by default (on Linux), but
> they shouldn't be treated as errors.
It's good at times to not treat them as errors, so I installed the
attached patch to add that capability more clearly, with a new
configure-time option --enable-gcc-warnings=warn-only. The attached
patch makes this new option the default if you have a Git checkout of
Emacs and GCC 5.3 or later. This shouldn't affect Eli any time soon,
since he uses an old compiler.
If this patch causes trouble by generating too many warnings on some
platforms, we can dial it back by suppressing warnings on those
platforms. But the latest GNU/Linux platforms running the latest GTK
should be warnings-free.
As others have noted in this thread, -Wall generates too many warnings.
The --enable-gcc-warnings option suppresses GCC warnings that are false
alarms for Emacs. It also enables some warnings that -Wall does not, but
which work well with Emacs.
[-- Attachment #2: 0001-Enable-GCC-warnings-in-developer-builds.patch --]
[-- Type: application/x-patch, Size: 5591 bytes --]
next prev parent reply other threads:[~2016-04-05 15:12 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 ` -Wall Paul Eggert
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 ` Paul Eggert [this message]
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=5703D5F2.4000708@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).