Home
last modified time | relevance | path

Searched refs:implications (Results 1 – 20 of 20) sorted by relevance

/llvm-project-15.0.7/llvm/test/CodeGen/X86/
H A D2011-12-26-extractelement-duplicate-load.ll5 ; twice: it has non-obvious performance implications, and
/llvm-project-15.0.7/openmp/docs/optimizations/
H A DOpenMPOpt.rst47 OpenMP programs. Unfortunately, this has significant performance implications
96 These optimizations can have very large performance implications. Both of these
/llvm-project-15.0.7/libc/docs/
H A Dindex.rst22 - The creation of fully static binaries without license implications.
/llvm-project-15.0.7/llvm/docs/HistoricalNotes/
H A D2001-02-13-Reference-MemoryResponse.txt43 keen to explore the implications of LLVM for mobile devices. Both bytecode
/llvm-project-15.0.7/libcxx/docs/DesignDocs/
H A DDebugMode.rst17 Since the debug mode has ABI implications, users should compile their whole program,
/llvm-project-15.0.7/clang/include/clang/Basic/
H A DSanitizers.def137 // ABI or address space layout implications, and only catch undefined behavior.
/llvm-project-15.0.7/llvm/docs/
H A DCFIVerify.rst51 type). This type of directive has no security implications, but may present
H A DScudoHardenedAllocator.rst323 type of function that was called to allocate it. Security implications of such
H A DLoopTerminology.rst261 There are few key implications of the definitions given above which
H A DSpeculativeLoadHardening.md960 functions. This avoids direct ABI implications by using a side channel between
H A DCodeGenerator.rst89 This design has two important implications. The first is that LLVM can support
H A DLangRef.rst609 corresponding pointer types, but there are additional implications to be
/llvm-project-15.0.7/mlir/docs/Dialects/
H A DVector.md321 There are multiple tradeoffs involved that mix implications on the programming
344 the most minor dimensions (see the bigger picture in implications on
401 The implications on codegen are as follows:
422 Decisions made at the MLIR level will have implications at a much later stage in
/llvm-project-15.0.7/polly/lib/External/pet/include/
H A Dpet.h530 struct pet_implication **implications; member
/llvm-project-15.0.7/clang/docs/analyzer/developer-docs/
H A DRegionStore.rst157 store". This has important implications for any sort of liveness or
/llvm-project-15.0.7/llvm/docs/PDB/
H A DDbiStream.rst125 subtle implications on the algorithm used to look up type records.
/llvm-project-15.0.7/mlir/docs/Rationale/
H A DRationaleLinalgDialect.md149 implications of adopting any of the existing solutions, Linalg had the
574 implications on the
/llvm-project-15.0.7/clang/docs/
H A DControlFlowIntegrity.rst192 most compilers and should not have security implications, so we allow it by
/llvm-project-15.0.7/mlir/docs/Dialects/Linalg/
H A D_index.md149 The main implications are that:
/llvm-project-15.0.7/llvm/docs/Proposals/
H A DGitHubMove.rst914 detail how the tool works and various implications of its operation.