Home
last modified time | relevance | path

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

12

/wasmtime-44.0.1/cranelift/filetests/filetests/alias/
H A Dfence.clif1 test alias-analysis
6 ;; analysis to move accesses across them.
H A Dmultiple-blocks.clif1 test alias-analysis
H A Dcategories.clif1 test alias-analysis
H A Dpartial-redundancy.clif1 test alias-analysis
H A Dsimple-alias.clif1 test alias-analysis
H A Dextends.clif1 test alias-analysis
/wasmtime-44.0.1/cranelift/codegen/src/
H A Dalias_analysis.rs196 let mut analysis = AliasAnalysis { in new() localVariable
202 analysis.compute_block_input_states(func); in new()
203 analysis in new()
H A Dcontext.rs346 let mut analysis = AliasAnalysis::new(&self.func, &self.domtree); in replace_redundant_loads() localVariable
347 analysis.compute_and_update_aliases(&mut self.func); in replace_redundant_loads()
/wasmtime-44.0.1/docs/
H A Dexamples-debugging.md11 tools for post-mortem analysis.
H A Dexamples-debugging-core-dumps.md5 consumed by external tooling (such as [`wasmgdb`][wasmgdb]) for post-mortem analysis.
87 tooling to do post-mortem analysis of the failure.
H A Dexamples-core-dumps.md10 post-mortem analysis.
H A Dexamples-profiling-vtune.md9 appropriate for detailed analysis of your Wasm program.
20 For more information on VTune and the analysis tools it provides see its
148 - Start the analysis
H A Dcontributing-fuzzing.md60 for this in your rationale and analysis of the bug.
H A Dcontributing-architecture.md157 No inter-procedural analysis is done and each function is compiled as its
/wasmtime-44.0.1/cranelift/codegen/src/egraph/
H A Dmod.rs77 pub(crate) struct OptimizeCtx<'opt, 'analysis>
79 'analysis: 'opt,
91 pub(crate) alias_analysis: &'opt mut AliasAnalysis<'analysis>,
122 impl<'opt, 'analysis> OptimizeCtx<'opt, 'analysis>
124 'analysis: 'opt,
/wasmtime-44.0.1/cranelift/filetests/filetests/egraph/
H A Dnot_a_load.clif6 ;; to make sure the alias analysis machinery doesn't break when we have these odd
H A Dtry_call-mem-clobber.clif1 ; Regression test for the alias analysis not considering try_call to be a memory fence
/wasmtime-44.0.1/cranelift/filetests/filetests/inline/
H A Dstack-maps-opt.clif5 ;; Test that, after inlining, alias analysis can boil away some GC ref stack
/wasmtime-44.0.1/cranelift/isle/
H A DTODO10 - More in-depth fallibility analysis (avoid failure edges where possible)
H A DREADME.md499 Semantic analysis performs type checking, figures out which rules apply to which
/wasmtime-44.0.1/tests/disas/component-model/
H A Dunsafe-intrinsics-used.wat25 ;; to ensure that they are rooted in that analysis and we do end up with
/wasmtime-44.0.1/crates/c-api/
H A DCMakeLists.txt153 option(ENABLE_CODE_ANALYSIS "Run code analysis" OFF)
/wasmtime-44.0.1/cranelift/
H A Drustc.md38 very powerful without the need for complex alias analysis logic.
/wasmtime-44.0.1/cranelift/codegen/src/opts/
H A Dextends.isle16 ;; is like a cheap version of known-bits analysis.)
/wasmtime-44.0.1/cranelift/docs/
H A Dcompare-llvm.md37 library of code analysis and transformation passes operate on LLVM IR.

12