This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: proposal to clean up @node Warning Options in invoke.texi
Chris Pickett <chris.pickett@mail.mcgill.ca> writes:
| Gabriel Dos Reis wrote:
| > "Manuel López-Ibáñez" <lopezibanez@gmail.com> writes:
| > [...]
| > | > I assume the -Wno-xxx that are set by default would be moved to
| > the
| > | > "default" section?
|
| My guess is that there is a misunderstanding here.
most probably :-)
| > | Warnings that are not active by default are obviously disabled,
| > | there is no need to mention them.
| > I don't understand. Please explain further.
|
| I'll try (since I agree). The default section should only list those
| options that are enabled by default. Anything not listed there is
| clearly not enabled by default.
|
| All that I'm proposing is that:
|
| -Wno-multichar
| Do not warn if a multicharacter constant ('FOO') is used.
| ...
|
| becomes:
|
| The following options are enabled by default:
| ...
| -Wmultichar
| ...
|
| ...
|
| -Wmultichar
| Warn if a multicharacter constant ('FOO') is used.
| ...
| This option is enabled by default.
|
| (using "enabled" for my original "implies").
I agree with this. However, I also agree with Tom's point that we
must have cross-references/index of all options (both the
affirmative and the negative forms).
See
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30330
-- Gaby