manywarnings: enable nicer gcc warning messages
authorEric Blake <eblake@redhat.com>
Tue, 24 Sep 2013 12:33:40 +0000 (06:33 -0600)
committerEric Blake <eblake@redhat.com>
Tue, 24 Sep 2013 12:33:40 +0000 (06:33 -0600)
commit4a5ee89c8a8be7350a8fd8ca1bacb196a190e492
treea03801e193df85b61277282b2c01a73559ac0164
parentaa20227c9f103f44a2a05229aa1bdbd41d387d1e
manywarnings: enable nicer gcc warning messages

With gcc 4.3.4, -Wdisabled-optimization is noisy unless you also
use -funit-at-a-time.

With gcc 4.4.7, there is no indication which warning option
triggered a particular message unless you also use
-fdiagnostics-show-option.

Both of these options are default in newer gcc (such as 4.8.1);
but including them in the list of possible warnings makes the
experience nicer on older platforms.

* m4/manywarnings.m4 (gl_MANYWARN_ALL_GCC): Older gcc requires
some -f options for optimal warnings.

Signed-off-by: Eric Blake <eblake@redhat.com>
ChangeLog
m4/manywarnings.m4