This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: proposal to clean up @node Warning Options in invoke.texi


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.


| 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").

If you meant something else in addition, can you give an example?

As far as I can tell, Manuel's original response was saying that one should not list -Wno-strict-prototypes in the default section on the basis of -Wstrict-prototypes not being default.

Thanks,
Chris


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]