public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-9897] analyzer: fixes to internal docs
@ 2024-04-10 20:46 David Malcolm
0 siblings, 0 replies; only message in thread
From: David Malcolm @ 2024-04-10 20:46 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:7f6599a201be2a3f7d1d799087e4ba283ec0bee8
commit r14-9897-g7f6599a201be2a3f7d1d799087e4ba283ec0bee8
Author: David Malcolm <dmalcolm@redhat.com>
Date: Wed Apr 10 16:43:28 2024 -0400
analyzer: fixes to internal docs
gcc/ChangeLog:
* doc/analyzer.texi: Various tweaks.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
Diff:
---
gcc/doc/analyzer.texi | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/analyzer.texi b/gcc/doc/analyzer.texi
index 8eb40272cb7..b53096e7b7d 100644
--- a/gcc/doc/analyzer.texi
+++ b/gcc/doc/analyzer.texi
@@ -21,6 +21,9 @@
@subsection Overview
+At a high-level, we're doing coverage-guided symbolic execution of the
+user's code.
+
The analyzer implementation works on the gimple-SSA representation.
(I chose this in the hopes of making it easy to work with LTO to
do whole-program analysis).
@@ -55,7 +58,9 @@ Next is the heart of the analyzer: we use a worklist to explore state
within the supergraph, building an "exploded graph".
Nodes in the exploded graph correspond to <point,@w{ }state> pairs, as in
"Precise Interprocedural Dataflow Analysis via Graph Reachability"
- (Thomas Reps, Susan Horwitz and Mooly Sagiv).
+ (Thomas Reps, Susan Horwitz and Mooly Sagiv) - but note that
+we're not using the algorithm described in that paper, just the
+``exploded graph'' terminology.
We reuse nodes for <point, state> pairs we've already seen, and avoid
tracking state too closely, so that (hopefully) we rapidly converge
@@ -499,7 +504,8 @@ which dumps a @file{SRC.eg.txt} file containing the full @code{exploded_graph}.
Assuming that you have the
@uref{https://gcc-newbies-guide.readthedocs.io/en/latest/debugging.html,,python support scripts for gdb}
-installed, you can use:
+installed (which you should do, it makes debugging GCC much easier),
+you can use:
@smallexample
(gdb) break-on-saved-diagnostic
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-04-10 20:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-10 20:46 [gcc r14-9897] analyzer: fixes to internal docs David Malcolm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).