Home
last modified time | relevance | path

Searched refs:exploded (Results 1 – 25 of 28) sorted by relevance

12

/netbsd-src/external/gpl3/gcc.old/dist/gcc/analyzer/
H A Danalyzer.opt27 The maximum number of 'after supernode' exploded nodes within the analyzer per supernode, before te…
31 The maximum number of exploded nodes per program point within the analyzer, before terminating anal…
111 Avoid combining multiple statements into one exploded edge.
157 fdump-analyzer-exploded-graph
159 Dump the analyzer exploded graph to a SRCFILE.eg.dot file.
161 fdump-analyzer-exploded-nodes
163 Emit diagnostics showing the location of nodes in the exploded graph.
165 fdump-analyzer-exploded-nodes-2
167 Dump a textual representation of the exploded graph to SRCFILE.eg.txt.
169 fdump-analyzer-exploded-nodes-3
[all …]
/netbsd-src/external/gpl3/gcc/dist/gcc/analyzer/
H A Danalyzer.opt27 The maximum number of 'after supernode' exploded nodes within the analyzer per supernode, before te…
31 The maximum number of exploded nodes per program point within the analyzer, before terminating anal…
55 The maximum depth of exploded nodes that should appear in a dot dump before switching to a less ver…
167 Avoid combining multiple statements into one exploded edge.
217 fdump-analyzer-exploded-graph
219 Dump the analyzer exploded graph to a SRCFILE.eg.dot file.
221 fdump-analyzer-exploded-nodes
223 Emit diagnostics showing the location of nodes in the exploded graph.
225 fdump-analyzer-exploded-nodes-2
227 Dump a textual representation of the exploded graph to SRCFILE.eg.txt.
[all …]
H A DChangeLog172 * exploded-graph.h (feasibility_state::dump_to_pp): New decl.
597 * exploded-graph.h (impl_region_model_context::add_note): New
729 * exploded-graph.h (impl_region_model_context::get_stmt): New.
1195 * exploded-graph.h (impl_region_model_context::get_taint_map):
1342 * exploded-graph.h
1595 * exploded-graph.h (exploded_graph::create_dynamic_call): Rename to...
1632 * exploded-graph.h (class dynamic_call_info_t): New class.
1983 * exploded-graph.h (impl_region_model_context::warn): Return bool.
2061 * analyzer.opt (fdump-analyzer-exploded-paths): New.
2068 * exploded-graph.h (exploded_path::dump_to_pp): Add ext_state
[all …]
/netbsd-src/external/gpl3/gcc/dist/gcc/doc/
H A Danalyzer.texi55 within the supergraph, building an "exploded graph".
56 Nodes in the exploded graph correspond to <point,@w{ }state> pairs, as in
62 on a final exploded graph, and terminate the analysis. We also bail
63 out if the number of exploded <end-of-basic-block, state> nodes gets
81 CFG and supergraph, with points (and thus potentially exploded nodes)
83 By default the exploded graph merges multiple consecutive statements
84 in a supernode into one exploded edge to minimize the size of the
85 exploded graph. This can be suppressed via
92 stack of callsites below them, so that paths in the exploded graph
101 Nodes and edges in the exploded graph are called ``exploded nodes'' and
[all …]
H A Dinvoke.texi432 -fdump-analyzer-exploded-graph @gol
433 -fdump-analyzer-exploded-nodes @gol
434 -fdump-analyzer-exploded-nodes-2 @gol
435 -fdump-analyzer-exploded-nodes-3 @gol
436 -fdump-analyzer-exploded-paths @gol
10077 Internally the analyzer builds an ``exploded graph'' that combines
10099 ``exploded graph''. With @option{-fno-analyzer-state-merge} this
10180 @item -fdump-analyzer-exploded-graph
10181 @opindex fdump-analyzer-exploded-graph
10182 Dump a representation of the ``exploded graph'' suitable for viewing with
[all …]
H A Dgccint.info46979 within the supergraph, building an "exploded graph". Nodes in the
46980 exploded graph correspond to <point, state> pairs, as in "Precise
46986 final exploded graph, and terminate the analysis. We also bail out if
46987 the number of exploded <end-of-basic-block, state> nodes gets larger
47003 CFG and supergraph, with points (and thus potentially exploded nodes)
47005 the exploded graph merges multiple consecutive statements in a supernode
47006 into one exploded edge to minimize the size of the exploded graph. This
47012 the stack of callsites below them, so that paths in the exploded graph
47021 Nodes and edges in the exploded graph are called "exploded nodes" and
47022 "exploded edges" and often referred to in the code as 'enodes' and
[all …]
H A Dgcc.info761 -fdump-analyzer-exploded-graph
762 -fdump-analyzer-exploded-nodes
763 -fdump-analyzer-exploded-nodes-2
764 -fdump-analyzer-exploded-nodes-3
765 -fdump-analyzer-exploded-paths
9084 Internally the analyzer builds an "exploded graph" that combines
9103 "exploded graph". With '-fno-analyzer-state-merge' this merging
9175 '-fdump-analyzer-exploded-graph'
9176 Dump a representation of the "exploded graph" suitable for viewing
9180 '-fdump-analyzer-exploded-nodes'
[all …]
/netbsd-src/external/gpl3/gcc.old/dist/gcc/doc/
H A Danalyzer.texi50 within the supergraph, building an "exploded graph".
51 Nodes in the exploded graph correspond to <point,@w{ }state> pairs, as in
57 on a final exploded graph, and terminate the analysis. We also bail
58 out if the number of exploded <end-of-basic-block, state> nodes gets
76 CFG and supergraph, with points (and thus potentially exploded nodes)
78 By default the exploded graph merges multiple consecutive statements
79 in a supernode into one exploded edge to minimize the size of the
80 exploded graph. This can be suppressed via
87 stack of callsites below them, so that paths in the exploded graph
96 Nodes and edges in the exploded graph are called ``exploded nodes'' and
[all …]
H A Dinvoke.texi399 -fdump-analyzer-exploded-graph @gol
400 -fdump-analyzer-exploded-nodes @gol
401 -fdump-analyzer-exploded-nodes-2 @gol
402 -fdump-analyzer-exploded-nodes-3 @gol
8473 Internally the analyzer builds an ``exploded graph'' that combines
8495 ``exploded graph''. With @option{-fno-analyzer-state-merge} this
8576 @item -fdump-analyzer-exploded-graph
8577 @opindex fdump-analyzer-exploded-graph
8578 Dump a representation of the ``exploded graph'' suitable for viewing with
8583 @item -fdump-analyzer-exploded-nodes
[all …]
H A Dgccint.info45336 within the supergraph, building an "exploded graph". Nodes in the
45337 exploded graph correspond to <point, state> pairs, as in "Precise
45343 final exploded graph, and terminate the analysis. We also bail out if
45344 the number of exploded <end-of-basic-block, state> nodes gets larger
45360 CFG and supergraph, with points (and thus potentially exploded nodes)
45362 the exploded graph merges multiple consecutive statements in a supernode
45363 into one exploded edge to minimize the size of the exploded graph. This
45369 the stack of callsites below them, so that paths in the exploded graph
45378 Nodes and edges in the exploded graph are called "exploded nodes" and
45379 "exploded edges" and often referred to in the code as 'enodes' and
[all …]
H A Dgcc.info730 -fdump-analyzer-exploded-graph
731 -fdump-analyzer-exploded-nodes
732 -fdump-analyzer-exploded-nodes-2
733 -fdump-analyzer-exploded-nodes-3
7682 Internally the analyzer builds an "exploded graph" that combines
7701 "exploded graph". With '-fno-analyzer-state-merge' this merging
7773 '-fdump-analyzer-exploded-graph'
7774 Dump a representation of the "exploded graph" suitable for viewing
7778 '-fdump-analyzer-exploded-nodes'
7779 Emit diagnostics showing where nodes in the "exploded graph" are in
[all …]
/netbsd-src/external/bsd/openldap/dist/contrib/ldaptcl/
H A DneoXldap.c1295 char **exploded, **p; local
1310 exploded = ldap_explode_dn(param, nonames);
1311 for (p = exploded; *p; p++) {
1318 ldap_value_free(exploded);
1326 ldap_value_free(exploded);
1332 ldap_value_free(exploded);
1337 ldap_value_free(exploded);
/netbsd-src/external/apache2/llvm/dist/clang/lib/StaticAnalyzer/
H A DREADME.txt25 node in an exploded graph (ExplodedGraph). The term "exploded" comes
/netbsd-src/usr.bin/make/
H A Dmain.c156 char *exploded, *ep; in explode() local
166 exploded = bmake_malloc((size_t)(p - flags) * 3 + 1); in explode()
167 for (p = flags, ep = exploded; *p != '\0'; p++) { in explode()
173 return exploded; in explode()
/netbsd-src/external/apache2/llvm/dist/clang/include/clang/StaticAnalyzer/Core/
H A DAnalyzerOptions.def369 "top level function (for each exploded graph). 0 means no limit.",
/netbsd-src/external/apache2/llvm/dist/clang/include/clang/Driver/
H A DOptions.td4614 HelpText<"Display exploded graph using GraphViz">,
4617 HelpText<"Dump exploded graph to the specified file">,
/netbsd-src/games/fortune/datfiles/
H A Dlimerick-o.real3591 His asshole exploded,
H A Dfortunes7028 Imagine if every Thursday your shoes exploded if you tied them the
16279 fired myself into it, at oblivious speed, and it exploded, and sparkled and it
H A Dfortunes21369 Whereupon the Clear Light of Illumination exploded upon Ken, and he
1376 Whereupon the Clear Light of Illumination exploded upon the monk,
1382 Whereupon the Clear Light of Illumination exploded upon the
25631 Imagine if every Thursday your shoes exploded if you tied them the usual
33580 1986, as the shuttle Challenger exploded within view
/netbsd-src/external/gpl3/gcc/dist/gcc/
H A DChangeLog-202038264 (-fdump-analyzer-exploded-graph): New warning.
38265 (-fdump-analyzer-exploded-nodes): New warning.
38266 (-fdump-analyzer-exploded-nodes-2): New warning.
38267 (-fdump-analyzer-exploded-nodes-3): New warning.
H A DChangeLog-200912408 * expr.c (expand_expr_real_2): New function taking exploded
13137 around an exploded simple expression.
13149 to take an exploded expression.
H A DFSFChangeLog.109026 exploded ADDR_VEC.
H A DChangeLog-202120136 * doc/invoke.texi (-fdump-analyzer-exploded-paths): New.
/netbsd-src/external/gpl3/gcc.old/dist/gcc/
H A DFSFChangeLog.109026 exploded ADDR_VEC.
/netbsd-src/share/dict/
H A Dweb2a71970 well-exploded

12