@@ -28,6 +28,13 @@ also accepted (with equivalent behavior). Analyzer options and checker options
28
28
can be freely intermixed here because it's easy to recognize that checker
29
29
option names are always prefixed with ``some.groups.NameOfChecker:``.
30
30
31
+ .. warning::
32
+ This is an internal interface, Clang does not intend to preserve backwards
33
+ compatibility or announce breaking changes within the flags accepted by
34
+ ``clang -cc1``. However, ``-analyzer-config`` survived many years without
35
+ significant changes and there is no "more official" interface for
36
+ configuring the analyzer options.
37
+
31
38
With the clang driver
32
39
---------------------
33
40
@@ -61,6 +68,10 @@ note the distinction that the ``clang`` *driver* requires ``--analyze`` (double
61
68
dashes) while the ``clang -cc1`` *compiler frontend* requires ``-analyze``
62
69
(single dash).
63
70
71
+ .. note::
72
+ The flag ``-Xanalyzer`` is equivalent to ``-Xclang`` in these situations
73
+ (but doesn't forward other options of the clang frontend).
74
+
64
75
With CodeChecker
65
76
----------------
66
77
@@ -89,9 +100,11 @@ List of analyzer options
89
100
========================
90
101
91
102
.. warning::
92
- These options are primarily intended for development purposes. Changing
93
- their values may drastically alter the behavior of the analyzer, and may
94
- even result in instabilities or crashes!
103
+ These options are primarily intended for development purposes and
104
+ non-default values are usually unsupported. Changing their values may
105
+ drastically alter the behavior of the analyzer, and may even result in
106
+ instabilities or crashes! Crash reports are welcome and depending on the
107
+ severity they may be fixed.
95
108
96
109
..
97
110
The contents of this section are automatically generated by the script
0 commit comments