[Bug other/7549] gcc3.1: Documentation glitches in info-files

[martin.jost@icn.siemens.de]

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-02 10:15 -------
Daras comments marked with ">"

1. -Wall:
>I'm not sure what the issue you describe here is. Examining the online docs, 
>which I assume are similar to the texinfo ones, -Wall says:
>-Wall      
>All of the above -W options combined. [...]

Yes, that's clear. My problem was the ordering for sequential reading.
If you read the options-section for warnings/errors in sequential order, all 
the "nitty gritty options" are explained _first_, _followed_ by -Wall.
I would like to see a sort of "forward reference" of the kind:
"Please note that the option "-Wall" (see below) will switch on all of the 
following options:
- ...
- ...
"
(And (I would like it) a remark: "Switched on by '-Wall'" at the relevant 
option)

I read all the options (sequentially), trying to decide which one to use; so -
Wall came as big suprise to me...


2. -fdata-sections and -ffunction-sections 
>Furthermore, -fdata-sections and -ffunction-sections are included in the 
>manual as global 
>options, and are not specifically mentioned to support hp-ux. Do you think we 
>should specify which targets they do not support?

The problem is, that it is explicitely mentioned, that HPPA _is_ supported, 
when in fact it doesn't seem to be:

Form the info-file:
"
`-ffunction-sections'
`-fdata-sections'
[...]
HPPA processors running HP-UX and Sparc processors running
=============================
     Solaris 2 have linkers with such optimizations.
               =====================================
"

> P.S. We really need to have a section for documentation bugs...

Yes, I agree !

P.S.:
I hope, I succeded this time to make my point clear.
Sorry for the late reply, I had been on holiday.
Thanks for your work on this !




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.