This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/7549] gcc3.1: Documentation glitches in info-files
- From: "martin dot jost at icn dot siemens dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jun 2003 11:41:00 -0000
- Subject: [Bug other/7549] gcc3.1: Documentation glitches in info-files
- References: <20020809034601.7549.martin.jost@icn.siemens.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7549
------- Additional Comments From martin.jost@icn.siemens.de 2003-06-05 11:40 -------
Ahh, sorry, I didn't got, that you are asking for the references in the manual.
Here they are:
===================== -Wall ===================================================
http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/Warning-Options.html#Warning%20Options
"
-Wall
All of the above -W options combined [...]
"
This comes waayyy down on the page.
As mentioned I would like to a see a reference to -Wall at the beginning of
this section and probably a note coming with each of the option, if it is
included in -Wall. (This would make it easier to decide which -W... to use)
Funnily there are already some forward references to Wall:
"-Wformat is included in -Wall. "
"-Wnonnull is included in -Wall and -Wformat."
"-Wstrict-aliasing [...] It is included in -Wall."
For the optimization-options this is already done !
See http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/Optimize-Options.html#Optimize%
20Options
"
-O turns on the following optimization flags:
-fdefer-pop
[...]
-fcprop-registers
"
And (e.g.)
"
-fforce-mem
[...]
Enabled at levels -O2, -O3, -Os.
"
=================== -ftrapv =================================================
Has already been moved to "Code generation options"
(Where it fits much better)
So this is solved.
============ `-ffunction-sections' `-fdata-sections' ========================
There is no mentioning of HPPA here any more. So this is also solved.
Martin
P.S.:
Thanks for following up through all the miss-understandings so far !
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.