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

[Chris Pickett]

Hi,

For one reason or another, I have spent a fair amount of time reading 
and getting confused by the warnings documentation.  This applies to the 
optimizations as well, but I thought I would start with the warnings. 
Today I sat down and created a dependency graph for all of the options 
in this node.  I made this at first for my own benefit, and then 
realized that other people might be interested in the information.

I have attached the graph.  I am asking for one or more people to 
comment on its correctness, and what I consider to be errors, as 
indicated in comments.

Then I have the following proposal for cleaning up the options node in 
invoke.texi:

1.  Create a default section, at the top, and put all options enabled by 
default there.

2.  Try to group options so that they are closer to other connected 
nodes in the graph.

3.  Get rid of the -Wno-xxx option listings, since it is not always the 
case that -Wxxx is enabled by "default", and this just ends up being 
rather confusing.  Instead, explain in the default section that 
everything there can be disabled with -Wno-xxx.

4.  For each option, specify connected options systematically, perhaps 
using the syntax I invented, perhaps using a different and more natural 
(i.e. plain old English) syntax.

5.  Fix what I have labelled as errors.

In a dream world where I had infinite time, I would invent a grammar for 
specifying relationships between options and then use that to generate 
number 4 above, and also use it to generate the option parsing bits of 
the front end.

Cheers,
Chris
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gcc_warnings.txt
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20061028/bfcadcf6/attachment.txt>