[Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags

ricardolafabreu at gmail dot com gcc-bugzilla@gcc.gnu.org
Wed Dec 4 11:17:00 GMT 2019


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757

--- Comment #10 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
> 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 reason to avoid coupling between them and document it prominently
otherwise.

My outsider impression is that, ideally, turning on -W... flags should turn on
whatever analysis was needed, independently of optimization. It would make for
smoother UI because it would be more in line with the natural affordance of a
switch. I suppose the increase in compilation cost would be justified by the
request for more checking. I am sure there are reasons why this is unfeasible,
undesirable, too risky... Better highlighting in documentation would alleviate
the surprise.


More information about the Gcc-bugs mailing list