On Fri, Jul 15, 2016 at 02:56:05PM -0600, Jerry James wrote:
> On Fri, Jul 15, 2016 at 2:49 PM, Jan Kratochvil
> wrote:
> > I find safer to use -Werror for such kinds of warnings.
>
> Do you keep a list somewhere of which warnings to use with -Werror?
> I'm too lazy to keep such a list updated as
On Fri, Jul 15, 2016 at 2:49 PM, Jan Kratochvil
wrote:
> I find safer to use -Werror for such kinds of warnings.
Do you keep a list somewhere of which warnings to use with -Werror?
I'm too lazy to keep such a list updated as gcc adds more warnings,
even if I had one to start with. This script is
On Fri, 15 Jul 2016 22:46:23 +0200, Jerry James wrote:
> Attached is a little script I use when doing a mock build with gcc or
> g++, to see what warnings the compiler emitted. I usually ignore
> -Wunused* warnings, as those aren't usually dangerous, but I pay
> attention to -Wstrict-aliasing, for
Attached is a little script I use when doing a mock build with gcc or
g++, to see what warnings the compiler emitted. I usually ignore
-Wunused* warnings, as those aren't usually dangerous, but I pay
attention to -Wstrict-aliasing, for example. This is a way for me to
quickly see if any "dangerou
