Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: ricardolafabreu at gmail dot com
Target Milestone: ---
The documentation (man page for gcc 8.3.0 or
https://gcc.gnu.org/onlinedocs/gcc/) could be clearer in what
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #2 from Ricardo Abreu ---
Saying "-Wall enables all the warnings that [...]" is inaccurate. Unless you
consider a very specific interpretation of "enables". Then it is ambiguous,
because there are other valid (and probably more intuit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #3 from Ricardo Abreu ---
Note that I would classify this as a request for improvement rather than a bug.
A manual is not a specification, it is something that should inform users, and
its contents can be better or worse in achieving
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #5 from Ricardo Abreu ---
> It has an unambiguous meaning:
>
> $ gcc -Q --help=warnings | fgrep maybe-uninit
> -Wmaybe-uninitialized [disabled]
> $ gcc -Q --help=warnings -Wall | fgrep maybe-uninit
> -Wmaybe-uninit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #7 from Ricardo Abreu ---
Yes, the very next paragraph directs to tens of other paragraphs that mention
other switches. One has to read them SFINAE mode to discover the special
meaning of the general text. That may be considered stric
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #8 from Ricardo Abreu ---
Don't get me wrong, I have a lot of admiration for GCC and the people behind!
It approaches perfection to a level that is very unusual in software.
Still, that does not amount to saying it is perfect. There
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #10 from Ricardo Abreu ---
> Usually CLI applications don't have as many switches as GCC with as many
> non-trivial interactions between them.
True, but I am not sure I understand your point. To me that sounds like all the
more reas
