Home
last modified time | relevance | path

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

123456

/llvm-project/libcxx/docs/DesignDocs/
H A DTimeZone.rst13 contents of the IANA database, this page assumes the reader is familiar with
19 The data of the database is available on several platforms in different forms:
21 - Typically Unix systems ship the database as
25 These files don't provide the database version information. This information
36 the database version information. This information is needed for the functions
42 ``Rule`` is abbreviated to ``R``. This file contains the database version
47 The time zone database version number is also missing from ``TZif`` files.
48 Since the time zone database is supposed to contain both these informations,
53 contains the database version information needed for a conforming
58 ship the database, so they only need to adjust the packaging of their time zone
[all …]
/llvm-project/third-party/benchmark/
H A D.ycm_extra_conf.py40 database = ycm_core.CompilationDatabase(compilation_database_folder) variable
42 database = None variable
95 compilation_info = database.GetCompilationInfoForFile(
101 return database.GetCompilationInfoForFile(filename)
105 if database:
/llvm-project/mlir/utils/vscode/src/
H A DmlirContext.ts107 * Prepare a compilation database option for a server.
117 // If no databases were explicitly specified, default to a database in the
127 for await (let database of databases) { variable
128 database = await this.resolvePath(database, '', workspaceFolder);
137 databases.filter(database => database !== '');
139 (database) => `--${languageName}-compilation-database=${database}`));
[all...]
/llvm-project/clang/include/clang/Basic/
H A DBuiltinsSME.def1 //===--- BuiltinsSME.def - SME Builtin function database --------*- C++ -*-===//
9 // This file defines the SME-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 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 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 described in clang/Basic/Builtins.def.
H A DBuiltinsLoongArch.def1 //==- BuiltinsLoongArch.def - LoongArch Builtin function database -- C++ -*-==//
9 // This file defines the LoongArch-specific builtin function database. Users of
H A DBuiltinsHexagon.def
H A DBuiltinsX86_64.def
/llvm-project/libcxx/docs/
H A DImplementationDefinedBehavior.rst21 *remote time zone database*. Libc++ opts not to do that. Instead calling
24 *remote time zone database*,
26 *remote time zone database*.
28 This offers a way for users to update the *remote time zone database* and
/llvm-project/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/libc/benchmarks/distributions/
H A DREADME.md21 - `GoogleB` <-> `database 1`
25 - `GoogleQ` <-> `database 2`
26 - `GoogleS` <-> `database 3`
/llvm-project/clang/docs/
H A DJSONCompilationDatabase.rst32 Clang has the ability 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.
135 // command-line options related to the compilation database and input files.
173 database into its build directory:
/llvm-project/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
34 The tool can be also used with a compile commands database:
40 To select only a subset of files from the database, use the ``--filter`` flag:
80 Example usage for a project using a compile commands database:
/llvm-project/.github/workflows/
H A Dci-post-commit-analyzer-run.py25 database = json.load(open(db_path))
28 pool.map_async(run_analyzer, [k for k in database], error_callback=pool_error)
/llvm-project/clang-tools-extra/clang-include-fixer/find-all-symbols/tool/
H A Drun-find-all-symbols.py96 database = json.load(open(os.path.join(build_path, db_path)))
97 files = [entry["file"] for entry in database]
/llvm-project/clang/tools/clang-scan-deps/
H A DOpts.td28 defm compilation_database : Eq<"compilation-database", "Compilation database">;
/llvm-project/mlir/docs/Tools/
H A DMLIRLSP.md145 server relies on a compilation database to provide build-system information for
147 available for that file. This database allows for the server to interact with
152 A PDLL compilation database is a YAML file, conventionally named
172 using CMake and `mlir_pdll`, a compilation database is generally automatically
271 server relies on a compilation database to provide build-system information for
273 available for that file. This database allows for the server to interact with
278 A TableGen compilation database is a YAML file, conventionally named
298 When using CMake and `mlir_tablegen`, a compilation database is generally
455 [`pdll_compile_commands.yml` files](https://mlir.llvm.org/docs/Tools/MLIRLSP/#compilation-database)
490 …egen_compile_commands.yml` files](https://mlir.llvm.org/docs/Tools/MLIRLSP/#compilation-database-1)
/llvm-project/llvm/utils/gn/secondary/libcxx/
H A Dconfig.gni8 # Build timezone database as part of libc++experimental.
/llvm-project/clang/test/ClangScanDeps/
H A Doptimize-vfs-pch.m11 // RUN: clang-scan-deps -compilation-database %t/build/compile-commands-pch.json \
20 // RUN: clang-scan-deps -compilation-database %t/build/compile-commands-tu.json \
27 // RUN: not clang-scan-deps -compilation-database %t/build/compile-commands-tu-no-vfs-error.json \
37 // RUN: clang-scan-deps -compilation-database %t/build/compile-commands-tu1.json \
H A Dmissing-vfs.m5 // RUN: not clang-scan-deps -compilation-database %t/build/cdb.json \

123456