From: "Perry E. Metzger" <perry@piermont.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Philipp Stephani <phst@google.com>,
Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel@gnu.org
Subject: Re: [PATCH] Clean up a couple of compiler warnings
Date: Sun, 21 May 2017 16:47:09 -0400 [thread overview]
Message-ID: <20170521164709.7bfcaa11@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <CAArVCkT3G85=otipybsd_E14QFWHnr5W3w-ZVHJy82VQbeuD9g@mail.gmail.com>
On Sun, 21 May 2017 20:00:11 +0000 Philipp Stephani
<p.stephani2@gmail.com> wrote:
> For Clang, it'd probably be better to use -Weverything and then
> disable individual warnings with -Wno... instead of checking for
> the existence of every warning flag. That would make configure runs
> faster and the command line shorter.
clang's -Weverything is like an options lamp test. There's an
enormous number of things there, and many aren't even properly
documented. You really don't want to use it -- the sheer number of
things you'll need to disable is astonishing, and with every new
iteration of clang there's an ocean more flags there. I think this
solution should be avoided.
Perry
--
Perry E. Metzger perry@piermont.com
prev parent reply other threads:[~2017-05-21 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 20:24 [PATCH] Clean up a couple of compiler warnings Philipp Stephani
2017-05-18 20:40 ` Eli Zaretskii
2017-05-19 3:48 ` Paul Eggert
2017-05-19 6:53 ` Eli Zaretskii
2017-05-19 6:55 ` Paul Eggert
2017-05-19 9:31 ` Philipp Stephani
2017-05-21 6:07 ` Paul Eggert
2017-05-21 20:00 ` Philipp Stephani
2017-05-21 20:33 ` Paul Eggert
2017-05-23 10:17 ` Philipp Stephani
2017-05-23 17:36 ` Paul Eggert
2017-05-23 19:19 ` Eli Zaretskii
2017-05-23 19:21 ` Philipp Stephani
2017-05-21 20:47 ` Perry E. Metzger [this message]
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=20170521164709.7bfcaa11@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=phst@google.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).