| /llvm-project-15.0.7/clang-tools-extra/clangd/ |
| H A D | FeatureModule.h | 124 Facilities &facilities();
126 TUScheduler &scheduler() { return facilities().Scheduler; } in scheduler()
128 const SymbolIndex *index() { return facilities().Index; } in index()
130 const ThreadsafeFS &fs() { return facilities().FS; } in fs()
|
| H A D | FeatureModule.cpp | 20 FeatureModule::Facilities &FeatureModule::facilities() { in facilities() function in clang::clangd::FeatureModule
|
| /llvm-project-15.0.7/llvm/examples/Kaleidoscope/MCJIT/complete/ |
| H A D | README.txt | 21 caching facilities.
|
| /llvm-project-15.0.7/libc/src/__support/FPUtil/generic/ |
| H A D | README.md | 28 facilities). But, the general idea is very similar.
|
| /llvm-project-15.0.7/llvm/examples/Kaleidoscope/MCJIT/cached/ |
| H A D | README.txt | 27 caching facilities.
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/Generic/ |
| H A D | cu-ranges.ll | 16 ; FIXME: When we get better dumping facilities we'll want to elaborate here.
|
| /llvm-project-15.0.7/libcxx/include/ |
| H A D | semaphore | 77 functions. It avoids contention against users' own use of those facilities.
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | MeetupGuidelines.rst | 66 * Some co-working spaces provide their facilities for non-profit (i.e., you do
|
| H A D | Projects.rst | 13 these facilities, a ``Makefile`` from a project must do the following things:
|
| H A D | SupportLibrary.rst | 13 facilities are needed and the Support Library is the wrapper around those
|
| H A D | FAQ.rst | 129 facilities for lexical nor semantic analysis.
|
| H A D | CodingStandards.rst | 74 standard library facilities or LLVM support libraries whenever they are
76 on the standard library facilities and the LLVM support libraries as much as
91 We explicitly avoid some standard facilities, like the I/O streams, and instead
1256 makes the code **clearer**, because it is immediately obvious what facilities
|
| H A D | GarbageCollection.rst | 199 This section describes the garbage collection facilities provided by the
|
| /llvm-project-15.0.7/llvm/docs/HistoricalNotes/ |
| H A D | 2001-05-18-ExceptionHandling.txt | 56 Here is a motivating example that illustrates how these facilities could be
|
| /llvm-project-15.0.7/mlir/docs/ |
| H A D | SymbolsAndSymbolTables.md | 64 have a unique name, and provides facilities for looking up symbols by name.
|
| H A D | Quantization.md | 195 Not every application of quantization will use all of these facilities. Specifically, the
|
| H A D | PDLL.md | 70 not have nice facilities for indexing or naming the multiple results. Let's take
|
| /llvm-project-15.0.7/mlir/docs/Rationale/ |
| H A D | UsageOfConst.md | 52 pattern matching and binding facilities to do their work.
|
| H A D | RationaleGenericDAGRewriter.md | 117 metaprogramming (MLIR has similar facilities). Here's a simple example:
|
| /llvm-project-15.0.7/llvm/docs/GlobalISel/ |
| H A D | Legalizer.rst | 234 There are some composite rules for common situations built out of the above facilities:
|
| /llvm-project-15.0.7/llvm/docs/tutorial/ |
| H A D | BuildingAJIT1.rst | 151 global mutex, and error reporting facilities); An RTDyldObjectLinkingLayer,
|
| /llvm-project-15.0.7/llvm/docs/TableGen/ |
| H A D | BackGuide.rst | 23 complete reference manual, but rather a guide to using the facilities
|
| /llvm-project-15.0.7/lldb/docs/resources/ |
| H A D | test.rst | 592 addition to pdb's debugging facilities, lldb commands can be executed with the
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/ |
| H A D | Contributing.rst | 664 The plugins can use threads, TLS, or any other facilities available to in-tree
|
| /llvm-project-15.0.7/llvm/docs/Proposals/ |
| H A D | GitHubMove.rst | 54 space, Git server, code browsing, forking facilities, etc) for free.
|