Home
last modified time | relevance | path

Searched refs:database (Results 1 – 25 of 81) sorted by relevance

1234

/llvm-project-15.0.7/third-party/benchmark/
H A D.ycm_extra_conf.py35 database = ycm_core.CompilationDatabase( compilation_database_folder ) variable
37 database = None variable
89 compilation_info = database.GetCompilationInfoForFile(
94 return database.GetCompilationInfoForFile( filename )
98 if database:
/llvm-project-15.0.7/mlir/utils/vscode/src/
H A DmlirContext.ts113 for await (let database of databases) { variable
114 database = await this.resolvePath(database, '', workspaceFolder);
123 databases.filter(database => database !== '');
125 (database) => `--${languageName}-compilation-database=${database}`));
/llvm-project-15.0.7/clang/include/clang/Basic/
H A DBuiltinsSVE.def1 //===--- BuiltinsSVE.def - SVE Builtin function database --------*- C++ -*-===//
9 // This file defines the SVE-specific builtin function database. Users of
14 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsNEON.def1 //===--- BuiltinsNEON.def - NEON Builtin function database ------*- C++ -*-===//
9 // This file defines the NEON-specific builtin function database. Users of
14 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsXCore.def1 //===--- BuiltinsXCore.def - XCore Builtin function database ----*- C++ -*-===//
9 // This file defines the XCore-specific builtin function database. Users of
14 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsVE.def1 //===--- BuiltinsVE.def - VE Builtin function database ----------*- C++ -*-===//
9 // This file defines the VE-specific builtin function database. Users of
18 // The format of this database is decribed in clang/Basic/Builtins.def.
H A DBuiltinsBPF.def1 //===--- BuiltinsBPF.def - BPF Builtin function database --------*- C++ -*-===//
9 // This file defines the BPF-specific builtin function database. Users of
14 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsHexagon.def1 //===-- BuiltinsHexagon.def - Hexagon Builtin function database --*- C++ -*-==//
9 // This file defines the Hexagon-specific builtin function database. Users of
14 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsX86_64.def1 //===--- BuiltinsX86_64.def - X86-64 Builtin function database --*- C++ -*-===//
9 // This file defines the X86-64-specific builtin function database. Users of
14 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsWebAssembly.def1 // BuiltinsWebAssembly.def - WebAssembly builtin function database -*- C++ -*-//
10 /// This file defines the WebAssembly-specific builtin function database.
16 // The format of this database matches clang/Basic/Builtins.def.
H A DBuiltinsRISCVVector.def9 // This file defines the RISC-V-specific builtin function database. Users of
H A DOpenCLExtensionTypes.def8 // This file extends builtin types database with OpenCL extension types.
/llvm-project-15.0.7/libc/benchmarks/distributions/
H A DREADME.md21 - `GoogleB` <-> `database 1`
25 - `GoogleQ` <-> `database 2`
26 - `GoogleS` <-> `database 3`
/llvm-project-15.0.7/clang/tools/scan-build-py/
H A DREADME.md5 intercepted and logged into a [compilation database][1] and/or piped to
32 To generate a compilation database file goes like this:
36 To run the Clang static analyzer against a project with compilation database
47 To run the CTU analysis, a compilation database file has to be created:
51 To run the Clang Static Analyzer against a compilation database
107 The 2. and 3. generate the compilation database first, and filters out those
116 compilation database. `analyze-build` does only run the analyzer against the
/llvm-project-15.0.7/clang-tools-extra/docs/
H A Dclang-include-fixer.rst23 - Compilation database. Contains the compiler commands for any given file in a
41 symbol database in YAML format from a compilation database by parsing all
43 database for LLVM, any project built by CMake should follow similar steps.
54 $ ln -s $PWD/find_all_symbols_db.yaml path/to/llvm/source/ # Link database into the source tree.
55 …$ ln -s $PWD/compile_commands.json path/to/llvm/source/ # Also link compilation database if it's n…
108 and only search the symbol from database, which is faster than normal mode.
149 The identifier that should be typo corrected is then sent to the database, if a
H A Dclang-doc.rst24 compile command database for your project (for an example of how to do this
29 database:
/llvm-project-15.0.7/clang/docs/
H A DJSONCompilationDatabase.rst32 Clang has the ablity to generate compilation database fragments via
34 fragments together between ``[`` and ``]`` to create a compilation database.
43 `Bazel <https://bazel.build>`_ can export a compilation database via
57 A compilation database is a JSON file, which consist of an array of
87 compilation database. There can be multiple command objects for the
110 the build directory to detect the file and use the compilation database
H A DLibTooling.rst47 are different ways to create a compilation database, and we need to support all
58 and automatic location of the compilation database using source files paths.
128 // command-line options related to the compilation database and input files.
161 database into its build directory:
/llvm-project-15.0.7/clang/test/ClangScanDeps/
H A Dsubframework_header_dir_symlink.m11 // RUN: clang-scan-deps -compilation-database %t.cdb -j 1 -reuse-filemanager=0 | \
13 // RUN: clang-scan-deps -compilation-database %t.cdb -j 1 -reuse-filemanager=1 | \
H A Dheader_stat_before_open.m10 // RUN: clang-scan-deps -compilation-database %t.cdb -j 1 | \
/llvm-project-15.0.7/clang-tools-extra/clang-include-fixer/find-all-symbols/tool/
H A Drun-find-all-symbols.py89 database = json.load(open(os.path.join(build_path, db_path)))
90 files = [entry['file'] for entry in database]
/llvm-project-15.0.7/mlir/docs/Tools/
H A DMLIRLSP.md138 server relies on a compilation database to provide build-system information for
140 available for that file. This database allows for the server to interact with
145 A PDLL compilation database is a YAML file, conventionally named
164 using CMake and `mlir_pdll`, a compilation database is generally automatically
263 server relies on a compilation database to provide build-system information for
265 available for that file. This database allows for the server to interact with
270 A TableGen compilation database is a YAML file, conventionally named
289 When using CMake and `mlir_tablegen`, a compilation database is generally
433 [`pdll_compile_commands.yml` files](https://mlir.llvm.org/docs/Tools/MLIRLSP/#compilation-database)
467 …egen_compile_commands.yml` files](https://mlir.llvm.org/docs/Tools/MLIRLSP/#compilation-database-1)
/llvm-project-15.0.7/flang/include/flang/Frontend/
H A DCodeGenOptions.def1 //===--- CodeGenOptions.def - Code generation option database ----- C++ -*-===//
/llvm-project-15.0.7/mlir/test/mlir-pdll-lsp-server/
H A Dcompilation_database.test2 // RUN: mlir-pdll-lsp-server -pdll-compilation-database=%t.yml -lit-test < %s | FileCheck %s
/llvm-project-15.0.7/mlir/test/tblgen-lsp-server/
H A Dcompilation_database.test2 // RUN: tblgen-lsp-server -tablegen-compilation-database=%t.yml -lit-test < %s | FileCheck %s

1234