commit c9e275660a19c804dd8c591c73cb9b169a9d7573
Author: Tobias Burnus ... and
about
...
within a
alloc_size
allowing
-fanalyzer
to emit
@@ -887,7 +887,7 @@ __asm (".global __flmap_lock" "\n\t"
The warning
+ The warning
-Wanalyzer-out-of-bounds
has been extended so that, where possible, it will emit a text-based
diagram visualizing the spatial relationship between
@@ -899,9 +899,9 @@ __asm (".global __flmap_lock" "\n\t"
whether they overlap, are touching, are close or far apart;
which one is before or after in memory, the relative sizes involved,
the direction of the access (read vs write), and, in some cases,
- the values of data involved.
Such "text art" diagrams can be controlled (or suppressed) via a new
- -fdiagnostics-text-art-charset= option.
+ -fdiagnostics-text-art-charset=
option.
For example, given the out-of-bounds write in strcat
in:
@@ -953,17 +953,17 @@ it emits:
-fdiagnostics-format=
now adds indentation and newlines to reflect the logical JSON structure of the data. The previous compact behavior can be restored via the new option
- -fno-diagnostics-json-formatting.
+ -fno-diagnostics-json-formatting
.
This also applies to the older output format named "json".
-ftime-report
,
and a SARIF output format is requested via
- -fdiagnostics-format=,
+ -fdiagnostics-format=
,
then the timing and memory usage data is now written in JSON form into
the SARIF output, rather than as plain text to stderr.