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
"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?
| >
|
| No.
Why?
| Warnings that are not active by default are obviously disabled,
| there is no need to mention them.
I don't understand. Please explain further.
[...]
| > | -pedantic <-- -pedantic-errors
| >
| > -ansi (and corresponding -std= options) also implies pedwarns or
| > errors but not all.
| > Moreoverm, g++ -fpermissive issues warnings where it should be
| > issueing hard errors.
| >
|
| Why pedantic issues warnings in C and errors in C++
Please, consult the archive; we have been through that many times.
[...]
| > | -Winit-self <== -Wuninitialized # depends not only on -O1, but -O(1|2|3|s)
| >
| > I believe the correct understanding is that it depends on optimization
| > level different from -O0.
| >
|
| It seems to me that the only reason for Winit-self to exists is that
| people try to silence the -Wuninitialized warnings using the init-self
| hack and then other people have to work-around that hack.
I don't believe that explanation.
-- Gaby