[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Clean up a couple of compiler warnings
From: |
Perry E. Metzger |
Subject: |
Re: [PATCH] Clean up a couple of compiler warnings |
Date: |
Sun, 21 May 2017 16:47:09 -0400 |
On Sun, 21 May 2017 20:00:11 +0000 Philipp Stephani
<address@hidden> 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 address@hidden
- Re: [PATCH] Clean up a couple of compiler warnings, (continued)
- Re: [PATCH] Clean up a couple of compiler warnings, Eli Zaretskii, 2017/05/19
- Re: [PATCH] Clean up a couple of compiler warnings, Philipp Stephani, 2017/05/19
- Re: [PATCH] Clean up a couple of compiler warnings, Paul Eggert, 2017/05/21
- Re: [PATCH] Clean up a couple of compiler warnings, Philipp Stephani, 2017/05/21
- Re: [PATCH] Clean up a couple of compiler warnings, Paul Eggert, 2017/05/21
- Re: [PATCH] Clean up a couple of compiler warnings, Philipp Stephani, 2017/05/23
- Re: [PATCH] Clean up a couple of compiler warnings, Paul Eggert, 2017/05/23
- Re: [PATCH] Clean up a couple of compiler warnings, Eli Zaretskii, 2017/05/23
- Re: [PATCH] Clean up a couple of compiler warnings, Philipp Stephani, 2017/05/23
- Re: [PATCH] Clean up a couple of compiler warnings,
Perry E. Metzger <=