invoke.texi: update -fdiagnostics-show-cwe for analyzer

gcc/ChangeLog:
	* doc/invoke.texi (-fdiagnostics-show-cwe): Add note that some of
	the analyzer options provide CWE identifiers.

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 2837364ae16fb6d108ef5bdf63311f8d6a2abe16..4da4d045ce82f07b64bada77d2f52bdd1f01419c 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2020-01-14  David Malcolm  <dmalcolm@redhat.com>
+
+       * doc/invoke.texi (-fdiagnostics-show-cwe): Add note that some of
+       the analyzer options provide CWE identifiers.
+
 2020-01-14  David Malcolm  <dmalcolm@redhat.com>
 
        * tree-diagnostic-path.cc (path_summary::event_range::print):

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 180cde3542492d6cfc1f00551406681c1f1a41bb..d8b94d837a968954b985350da396ea6d4a477e25 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -4076,7 +4076,8 @@ the vertical bars and the ``char *'' and ``long int'' text).
 @opindex fdiagnostics-show-cwe
 Diagnostic messages can optionally have an associated
 @url{https://cwe.mitre.org/index.html, CWE} identifier.
-GCC itself does not do this for any of its diagnostics, but plugins may do so.
+GCC itself only provides such metadata for some of the @option{-fanalyzer}
+diagnostics.  GCC plugins may also provide diagnostics with such metadata.
 By default, if this information is present, it will be printed with
 the diagnostic.  This option suppresses the printing of this metadata.