This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Use "[warning enabled by default]" for default warnings
- From: Robert Dewar <dewar at adacore dot com>
- To: gcc-patches at gcc dot gnu dot org, rdsandiford at googlemail dot com
- Date: Sun, 09 Feb 2014 15:04:23 -0500
- Subject: Re: Use "[warning enabled by default]" for default warnings
- Authentication-results: sourceware.org; auth=none
- References: <87eh3c3vl1 dot fsf at talisman dot default>
On 2/9/2014 3:00 PM, Richard Sandiford wrote:
We print "[-Wfoo]" after a warning that was enabled by the -Wfoo option,
which is pretty clear. But for warnings that have no -W option we just
print "[enabled by default]", which leads to the question of _what_ is
enabled by default. As shown by:
http://gcc.gnu.org/ml/gcc/2014-01/msg00234.html
it invites the wrong interpretation for things like:
warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
IMO the natural assumption is that gnu++11 is enabled by default, which is
how Lars also read it.
There seemed to be support for using "warning enabled by default" instead,
so this patch does that. Tested on x86_64-linux-gnu. OK to install?
Sounds like an earthquake patch from the point of view of test suite
baselines!
I'll post an Ada patch separately.
Will definitely have a big impact on the Ada test suite. Fine to
post the Ada patch (which is of course trivial as a patch), but
we will have to coordinate installing it with a pass through
test base lines.