On 13/01/20 17:27 +0000, Martin Sebor wrote:
On 12/2/19 9:35 PM, Jonathan Wakely wrote:
PR driver/92757
* doc/invoke.texi (Warning Options): Add caveat about some warnings
depending on optimization settings.
The bug reporter wants this clarified. I'm not entirely convinced it's
necessary, but it doesn't seem to do any harm.
OK for trunk?
I think adding something to the manual about this interplay would
be useful but I'm not sure that saying only that some warnings have
this dependency will help all that much. I think each warning that
significantly depends on optimization should document it and,
ideally, explain to what extent. That way users will be clear on
what to expect. I suspect I might have been responsible for at least
some of the confusion here (I've added warnings that work both with
and without optimization but that do a much better job with it than
without), so I should probably take an AI to review the manual and
try to add some clarity.
Some of them already do say it, the bug report was that users
shouldn't have to read every individual option to learn that
diagnostic quality varies with optimisations.
