Home
last modified time | relevance | path

Searched refs:analysis (Results 1 – 25 of 639) sorted by relevance

12345678910>>...26

/netbsd-src/external/apache2/llvm/dist/llvm/docs/
H A DNewPassManager.rst150 When a pass runs on some IR, it also receives an analysis manager which it can
151 query for analyses. Querying for an analysis will cause the manager to check if
154 new result by calling the analysis's ``run()`` method, cache it, and return it.
155 You can also ask the analysis manager to only return an analysis if it's
158 The analysis manager only provides analysis results for the same IR type as
159 what the pass runs on. For example, a function pass receives an analysis
164 immutable global analysis. In these cases, the analysis manager can provide a
165 proxy to an outer or inner level analysis manager. For example, to get a
175 would have access to. To get access to an outer level IR analysis, you can
184 Getting direct access to an outer level IR analysis manager is not allowed.
[all …]
H A DAliasAnalysis.rst13 memory. There are many different algorithms for alias analysis and many
25 analysis information and the implementations providing it, and is designed to
27 are assumed to be flow-insensitive). In addition to simple alias analysis
40 class defines the interface that the various alias analysis implementations
162 analysis implementations and can be put to good use by various clients.
167 The ``pointsToConstantMemory`` method returns true if and only if the analysis
180 analysis can prove that the function never reads or writes to memory, or if the
187 The ``onlyReadsMemory`` method returns true for a function if analysis can prove
198 Writing a new alias analysis implementation for LLVM is quite straight-forward.
201 look at the `various alias analysis implementations`_ included with LLVM.
[all …]
H A DStackSafetyAnalysis.rst12 The primary purpose of the analysis is to be used by sanitizers to avoid
25 The analysis is implemented in two stages:
38 When used with ThinLTO, the global stage performs a whole program analysis over
44 The analysis is covered with lit tests.
H A DWritingAnLLVMPass.rst16 build the analysis results that are used by these transformations, and they
185 an analysis pass, for example dominator tree pass, then ``true`` is supplied as
276 OVERVIEW: llvm .bc -> .bc modular optimizer and analysis printer
350 analysis, but can provide information about the current compiler configuration.
373 provide the function to retrieve analysis result for, if the function pass does
375 for functions for which the analysis ran, e.g. in the case of dominators you
525 transformation or analysis work of your pass. As usual, a ``true`` value
576 should be used to access ``Function`` or ``Module`` level analysis information.
588 transformation or analysis work of your pass. As usual, a ``true`` value
629 should be used to access ``Function`` or ``Module`` level analysis information.
[all …]
H A DLexicon.rst22 analysis are so intertwined for C and especially C++), the typical
83 unable to use the pointer for reachability analysis. While a derived pointer
122 Garbage Collection. The practice of using reachability analysis instead of
144 reachability analysis.
156 Inter-Procedural Analysis. Refers to any variety of code analysis that
182 a "personality" function to do language specific analysis. Each function's
255 which the collector begins its reachability analysis. In the context of code
269 reachability analysis may proceed. It may be infeasible to provide this
H A DCFIVerify.rst40 code. The analysis of machine code is important as it ensures that any bugs
86 analysis. Non-executable sections do not require analysis as any execution
89 Suitable extensions may be made at a later date to include analysis for indirect
91 only experimental with an unstable ABI, making them unsuitable for analysis.
/netbsd-src/external/apache2/llvm/dist/llvm/docs/CommandGuide/
H A Dllvm-exegesis.rst27 scheduling models. To that end, we also provide analysis of the results.
115 EXAMPLE 3: analysis
124 $ llvm-exegesis -mode=analysis \
126 -analysis-clusters-output-file=/tmp/clusters.csv \
127 -analysis-inconsistencies-output-file=/tmp/inconsistencies.html
155 .. image:: llvm-exegesis-analysis.png
160 be shown. This does not invalidate any of the analysis results though.
186 .. option:: -mode=[latency|uops|inverse_throughput|analysis]
194 In `analysis` mode, you also need to specify at least one of the
195 `-analysis-clusters-output-file=` and `-analysis-inconsistencies-output-file=`.
[all …]
/netbsd-src/external/apache2/llvm/dist/clang/include/clang/StaticAnalyzer/Core/
H A DAnalyses.def35 ANALYSIS_DIAGNOSTICS(HTML, "html", "Output analysis results using HTML",
40 "Output analysis results using HTML (not allowing for multi-file bugs)",
43 ANALYSIS_DIAGNOSTICS(PLIST, "plist", "Output analysis results using Plists",
48 "Output analysis results using Plists (allowing for multi-file bugs)",
52 "Output analysis results using HTML wrapped with Plists",
55 ANALYSIS_DIAGNOSTICS(SARIF, "sarif", "Output analysis results using SARIF",
59 "Output analysis results using both SARIF and HTML "
63 ANALYSIS_DIAGNOSTICS(TEXT, "text", "Text output of analysis results to stderr",
69 "used in addition to other analysis types",
/netbsd-src/external/cddl/dtracetoolkit/dist/
H A DGuide45 Cpu/ Scripts for CPU analysis
47 Disk/ Scripts for disk I/O analysis
58 Kernel/ Scripts for kernel analysis
60 Locks/ Scripts for lock analysis
63 Mem/ Scripts for memory analysis
65 Net/ Scripts for network analysis
69 Proc/ Scripts for process analysis
74 System/ Scripts for system analysis
76 User/ Scripts for user based activity analysis
77 Zones/ Scripts for analysis by zone
H A DREADME45 Cpu/ Scripts for CPU analysis
47 Disk/ Scripts for disk I/O analysis
58 Kernel/ Scripts for kernel analysis
60 Locks/ Scripts for lock analysis
63 Mem/ Scripts for memory analysis
65 Net/ Scripts for network analysis
69 Proc/ Scripts for process analysis
74 System/ Scripts for system analysis
76 User/ Scripts for user based activity analysis
77 Zones/ Scripts for analysis by zone
/netbsd-src/external/apache2/llvm/dist/llvm/include/llvm/
H A DPassSupport.h37 #define INITIALIZE_PASS(passName, arg, name, cfg, analysis) \ argument
41 PassInfo::NormalCtor_t(callDefaultCtor<passName>), cfg, analysis); \
51 #define INITIALIZE_PASS_BEGIN(passName, arg, name, cfg, analysis) \ argument
58 #define INITIALIZE_PASS_END(passName, arg, name, cfg, analysis) \ argument
61 PassInfo::NormalCtor_t(callDefaultCtor<passName>), cfg, analysis); \
153 #define INITIALIZE_AG_PASS(passName, agName, arg, name, cfg, analysis, def) \ argument
159 PassInfo::NormalCtor_t(callDefaultCtor<passName>), cfg, analysis); \
173 #define INITIALIZE_AG_PASS_BEGIN(passName, agName, arg, n, cfg, analysis, def) \ argument
178 #define INITIALIZE_AG_PASS_END(passName, agName, arg, n, cfg, analysis, def) \ argument
181 PassInfo::NormalCtor_t(callDefaultCtor<passName>), cfg, analysis); \
/netbsd-src/external/apache2/llvm/dist/clang/docs/analyzer/user-docs/
H A DCrossTranslationUnit.rst5 Normally, static analysis works in the boundary of one translation unit (TU).
6 However, with additional steps and configuration we can enable the analysis to inline the definitio…
14 CTU analysis can be used in a variety of ways. The importing of external TU definitions can work wi…
15 files or generating the necessary AST structure on-demand, during the analysis of the main TU. Driv…
16 analysis can also be implemented in multiple ways. The most direct way is to specify the necessary …
21 PCH-based analysis
23 The analysis needs the PCH dumps of all the translations units used in the project.
27 is to use PCH-based analysis, as the lack of that extension signals that the entry is to be used as…
30 The analysis invocation must be provided with the directory which contains the dumps and the mappin…
104 Now everything is available for the CTU analysis.
[all …]
/netbsd-src/external/bsd/unbound/dist/testdata/clang-analysis.tdir/
H A Dclang-analysis.dsc1 BaseName: clang-analysis
3 Description: clang analysis
10 Pre: clang-analysis.pre
12 Test: clang-analysis.test
/netbsd-src/external/apache2/llvm/dist/clang/docs/
H A DThreadSafetyAnalysis.rst10 potential race conditions in code. The analysis is completely static (i.e.
11 compile-time); there is no run-time overhead. The analysis is still
16 Thread safety analysis works very much like a type system for multi-threaded
20 *guarded by* the mutex ``mu``, then the analysis will issue a warning whenever
23 the GUI thread, then the analysis will warn if other threads call those
60 This example demonstrates the basic concepts behind the analysis. The
69 analysis issues a warning. Thread safety analysis is not inter-procedural, so
72 locks ``this->mu``, it does not lock ``b.mu``. The analysis understands
76 unlock ``mu``. Every lock must have a corresponding unlock, and the analysis
85 To run the analysis, simply compile with the ``-Wthread-safety`` flag, e.g.
[all …]
H A DClangStaticAnalyzer.rst5 The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C…
6 It implements *path-sensitive*, *inter-procedural analysis* based on *symbolic execution* technique.
/netbsd-src/external/gpl3/gcc/dist/gcc/doc/
H A Dloop.texi17 variable analysis and number of iterations analysis).
20 * Loop representation:: Representation and analysis of loops.
26 * Number of iterations:: Number of iterations analysis.
27 * Dependency analysis:: Data dependency analysis.
33 @cindex Loop analysis
51 single latch. During loop analysis, headers of such loops are split and
56 that the analysis sometimes changes the CFG, and if you run it in the
106 changes to CFG will be performed in the loop analysis, in particular,
286 @item Many optimizations (value range analysis, final value
290 @item In induction variable analysis, it is not necessary to specify the
[all …]
/netbsd-src/external/gpl3/gcc.old/dist/gcc/doc/
H A Dloop.texi17 variable analysis and number of iterations analysis).
20 * Loop representation:: Representation and analysis of loops.
26 * Number of iterations:: Number of iterations analysis.
27 * Dependency analysis:: Data dependency analysis.
33 @cindex Loop analysis
51 single latch. During loop analysis, headers of such loops are split and
56 that the analysis sometimes changes the CFG, and if you run it in the
105 changes to CFG will be performed in the loop analysis, in particular,
285 @item Many optimizations (value range analysis, final value
289 @item In induction variable analysis, it is not necessary to specify the
[all …]
/netbsd-src/external/apache2/llvm/dist/clang/tools/scan-build-py/
H A DREADME.md44 How to use the experimental Cross Translation Unit analysis
47 To run the CTU analysis, a compilation database file has to be created:
52 with CTU analysis enabled, execute:
56 For CTU analysis an additional (external definition) collection-phase is required.
58 and the analysis phase. By doing this, the intermediate files used for
59 the analysis are kept on the disk in `./ctu-dir`.
61 # Collect and store the data required by the CTU analysis
108 modules which are not exists. So, it's suitable for incremental analysis during
/netbsd-src/external/cddl/dtracetoolkit/dist/Proc/
H A DReadme1 Proc - Process based analysis
3 This would include activity by PID, and syscall analysis.
/netbsd-src/external/apache2/llvm/dist/llvm/docs/HistoricalNotes/
H A D2000-12-06-MeetingSummary.txt15 analysis because the extra information can help limit the scope of
16 analysis.
28 information for one optimization. Alias analysis itself is typically
39 representation. This is one example of an analysis result that may be
65 packet type and length field before analysis information, to allow a
H A D2001-02-13-Reference-MemoryResponse.txt11 > could be very nice for analysis (pointer always points to the start of
13 > pointer type would be kept for C++ like semantics. Through analysis,
20 straightforward analysis. Let's include a reference type for now. But I'm
28 > A. If you do pointer analysis and realize that two stores are
H A D2001-02-13-Reference-Memory.txt20 could be very nice for analysis (pointer always points to the start of
22 pointer type would be kept for C++ like semantics. Through analysis,
28 A. If you do pointer analysis and realize that two stores are
/netbsd-src/external/gpl3/gcc.old/dist/gcc/analyzer/
H A Danalyzer.opt27 …of 'after supernode' exploded nodes within the analyzer per supernode, before terminating analysis.
31 …of exploded nodes per program point within the analyzer, before terminating analysis of that point.
35 …site can appear in a call stack within the analyzer, before terminating analysis of a call that wo…
119 Purge unneeded state during analysis.
123 Merge similar-enough states during analysis.
127 Enable transitivity of constraints during analysis.
131 Approximate the effect of function calls to simplify analysis.
/netbsd-src/external/apache2/llvm/dist/clang/lib/StaticAnalyzer/
H A DREADME.txt7 The analyzer library has two layers: a (low-level) static analysis
13 of the gore of the internal analysis engine.
28 Conceptually the analyzer does a reachability analysis through the
31 individual expressions. The analysis of an expression can cause the
59 Finally, individual Checkers work by also manipulating the analysis
134 [1] Precise interprocedural dataflow analysis via graph reachability,
138 [2] A memory model for static analysis of C programs, Z Xu, T
/netbsd-src/external/gpl3/gcc.old/dist/gcc/d/
H A DREADME.gcc4 They cover the lexical analysis, parsing, and semantic analysis of the

12345678910>>...26