| /llvm-project/.github/workflows/ |
| H A D | docs.yml | 4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
6 name: "Test documentation build"
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
[all...] |
| /llvm-project/flang/docs/ |
| H A D | GettingStarted.md | 1 <!--===- docs/GettingStarted.md
5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 -->
12 ---
14 ---
18 There are two ways to build flang. The first method is to build it at the same
19 time that you build all of the projects on which it depends. This is called
20 building in tree. The second method is to first do an in tree build to create
22 build, only build the flang code itself. This is called building standalone.
24 create the base build and base install areas, you can create multiple
[all …]
|
| /llvm-project/third-party/benchmark/ |
| H A D | README.md | 3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …st-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://githu…
33 [User Guide](docs/user_guide.md) for a more comprehensive feature overview.
35 …read the [Google Test documentation](https://github.com/google/googletest/blob/main/docs/primer.md)
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
45 [Additional Tooling Documentation](docs/tools.md)
47 [Assembly Testing Documentation](docs/AssemblyTests.md)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++11 to build,
56 The following minimum versions are required to build the library:
[all …]
|
| /llvm-project/clang-tools-extra/docs/clang-tidy/ |
| H A D | Contributing.rst | 5 :program:`clang-tidy` has several own checks and can run Clang static analyzer
8 Checks are organized in modules, which can be linked into :program:`clang-tidy`
9 with minimal or no code changes in :program:`clang-tidy`.
13 report them in a way similar to how Clang diagnostics work. A fix-it hint can be
16 The interface provided by :program:`clang-tidy` makes it easy to write useful
18 check, the rest of this document explains how to do this.
20 There are a few tools particularly useful when developing clang-tidy checks:
22 check, it will create the check, update the CMake file and create a test;
24 check;
[all...] |
| /llvm-project/compiler-rt/www/ |
| H A D | index.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
6 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
7 <title>"compiler-r
[all...] |
| /llvm-project/polly/www/ |
| H A D | get_started.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
5 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6 <title>Polly - Getting Started</title>
13 <!--#include virtual="menu.html.incl"-->
[all...] |
| /llvm-project/llvm/docs/ |
| H A D | TestSuiteGuide.md | 1 test-suite Guide
5 ---------
[all...] |
| H A D | GettingStarted.rst | 19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This
21 -- and from there into object files, using LLVM.
32 #. Check out LLVM (including subprojects like Clang):
34 * ``git clone https://github.com/llvm/llvm-project.git``
37 ``git clone --config core.autocrlf=false
38 https://github.com/llvm/llvm-project.git``
39 * To save storage and speed-up the checkout time, you may want to do a
40 `shallow clone <https://git-sc
[all...] |
| H A D | GettingInvolved.rst | 31 The LLVM project's code-review process.
34 The LLVM support policy for core and non-core components.
52 Describes how to use the llvm-project repository and code reviews on GitHub.
60 .. _development-process:
63 ------
[all...] |
| H A D | HowToAddABuilder.rst | 2 How To Add Your Build Configuration To LLVM Buildbot Infrastructure
8 This document contains information about adding a build configuration and
24 the build.
26 attached to this machine will be completely silent by default when the build
28 commits from the llvm-zorg repository.
51 maintains the build configuration. Generally, operational responsibility lies
52 with the "config owner". We do expect "resource owners" - who are generally
53 the contact listed in a workers attributes - to proxy requests to the relevant
61 Volunteers can provide their build machines to work as build worker
[all...] |
| H A D | HowToBuildWithPGO.rst | 2 How To Build Clang and LLVM with Profile-Guided Optimizations
8 PGO (Profile-Guided Optimization) allows your compiler to better optimize code
12 This guide walks you through how to build Clang with PGO, though it also applies
15 If you want to build other software with PGO, see the `end-user documentation
16 for PGO <https://clang.llvm.org/docs/UsersManual.html#profile-guided-optimization>`_.
22 See https://llvm.org/docs/AdvancedBuilds.html#multi-stage-pgo
29 compiler-rt. Despite the name, it performs four clean builds of Clang, so it
30 can take a while to run to completion. Please see the script's ``--help`` for
32 If you want to get the most out of PGO for a particular use-case (e.g. compiling
39 This script also supports a ``--dry-run`` option, which causes it to print
[all …]
|
| /llvm-project/clang/www/ |
| H A D | hacking.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
6 <META http-equiv="Content-Type" content="text/html; charset=utf-8">
11 pre { margin-left: 1.5em; }
15 <!-
[all...] |
| H A D | get_started.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
5 <META http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <title>Clang - Getting Started</title>
12 <!--#include virtual="menu.html.incl"-->
22 bugs on <a href="https://github.com/llvm/llvm-project/issues">the LLVM bug tracker</a>.</p>
29 <h2 id="build">Building Clang and Working with the Code</h2>
31 <h3 id="buildNix">On Unix-like Systems</h3>
33 <p>If you would like to check out and build Clang, the current procedure is as
40 <a href="https://llvm.org/docs/GettingStarted.html#requirements">
41 Getting Started with the LLVM System - Requirements</a>.</li>
[all …]
|
| /llvm-project/lldb/docs/resources/ |
| H A D | build.rst | 5 ----------
[all...] |
| /llvm-project/third-party/benchmark/docs/ |
| H A D | AssemblyTests.md | 21 * Add `// CHECK` lines to match against the verified assembly.
26 // CHECK-LABEL: test_add:
31 // CHECK: movl ExternInt(%rip), %eax
32 // CHECK: addl %eax
33 // CHECK: ret
40 [LLVM's Filecheck](https://llvm.org/docs/CommandGuide/FileCheck.html)
41 is used to test the generated assembly against the `// CHECK` lines
43 linked above for information on how to write `CHECK` directives.
48 correctness. `CHECK` directives don't have to match on the exact next line
50 bits of assembly. ([`CHECK-NEXT`](https://llvm.org/docs/CommandGuide/FileCheck.html#the-check-next-…
[all …]
|
| /llvm-project/clang/docs/ |
| H A D | HowToSetupToolingForLLVM.rst | 7 of specific tools using this infrastructure (e.g. ``clang-check``). This
14 Clang Tooling needs a compilation database to figure out specific build
17 invoking clang tools, you can either specify a path to a build directory
18 using a command line parameter ``-p`` or let Clang Tooling find this
20 build using CMake to use clang tools.
25 If you intend to use make to build LLVM, you should have CMake 2.8.6 or
29 make a build directory and run CMake from it:
31 .. code-block:: console
33 $ mkdir your/build/directory
34 $ cd your/build/directory
[all …]
|
| H A D | ClangCheck.rst | 8 .. code-block:: console
15 $ ~/clang/build/bin/clang-check snippet.cc -ast-dump --
16 Processing: /Users/danieljasper/clang/llvm/tools/clang/docs/snippet.cc.
17 /Users/danieljasper/clang/llvm/tools/clang/docs/snippet.cc:2:12: error: expected ';' at end of
26 …(FunctionDecl 0x7ff3a302a8d0 </Users/danieljasper/clang/llvm/tools/clang/docs/snippet.cc:1:1, line…
34 The '--' at the end is important as it prevents :program:`clang-check` from
36 use :program:`clang-check` in a project, see :doc:`HowToSetupToolingForLLVM`.
|
| /llvm-project/clang-tools-extra/docs/ |
| H A D | modularize.rst | 28 To build from source:
35 directions for how to build. With sources all checked out into the
36 right place the LLVM build will build Clang Extra Tools and their
39 * If using CMake, you can also use the ``modularize`` target to build
45 .. _Getting Started with the LLVM System: https://llvm.org/docs/GettingStarted.html
46 .. _Building LLVM with CMake: https://llvm.org/docs/CMake.html
47 .. _Clang Tools Documentation: https://clang.llvm.org/docs/ClangTools.html
52 Modularize will check for the following:
112 .. _module-ma
[all...] |
| /llvm-project/clang-tools-extra/ |
| H A D | CMakeLists.txt | 7 "Include static analyzer checks in clang-tidy" ON)
10 umbrella_lit_testsuite_begin(check-clang-tools)
14 set_property(GLOBAL APPEND PROPERTY LLVM_CLANG_TOOLS_LIT_EXTRA_ARGS "--vg")
18 add_subdirectory(clang-apply-replacements)
19 add_subdirectory(clang-reorder-field
[all...] |
| /llvm-project/llvm/utils/gn/ |
| H A D | README.rst | 13 *Warning* The GN build is experimental and best-effort. It might not work,
15 necessary. LLVM's official build system is CMake, if in doubt use that.
16 If you add files, you're expected to update the CMake build but you don't need
17 to update GN build files. Reviewers should not ask authors to update GN build
18 files. Keeping the GN build files up-to-date is on the people who use the GN
19 build.
23 which then shell out to ninja for the actual build.
25 The main motivation behind the GN build is that some people find it more
26 convenient for day-to-day hacking on LLVM than CMake. Distribution, building
27 just parts of LLVM, and embedding the LLVM GN build from other builds are
[all …]
|
| /llvm-project/libc/src/math/docs/ |
| H A D | add_math_function.md | 1 # How to add a new math function to LLVM-libc
14 - Add entry points `libc.src.math.func` to the following files:
19 - Add function specs to the file:
29 - Add `add_math_entrypoint_object(<func>)` to:
33 - Add function declaration (under `LIBC_NAMESPACE` namespace) to:
37 - Add function definition to:
41 - Add the corresponding `add_entrypoint_object` to:
45 - Add architectural specific implementations to:
52 - Floating point utilities and math functions that are also used internally are
57 - Thes
[all...] |
| /llvm-project/clang-tools-extra/docs/clang-tidy/checks/ |
| H A D | list.rst | 1 .. title:: clang-tidy - Clang-Tidy Checks
3 Clang-Tidy Checks
16 clang-analyzer/*
36 .. csv-table::
39 :doc:`abseil-cleanup-ctad <abseil/cleanup-ctad>`, "Yes"
40 :doc:`abseil-duratio
[all...] |
| /llvm-project/bolt/ |
| H A D | CMakeLists.txt | 25 # standalone build, copied from clang
34 # Assertions should follow llvm-config's.
42 find_program(LLVM_TABLEGEN_EXE "llvm-tblgen" ${LLVM_TOOLS_BINARY_DIR}
59 # Determine default set of targets to build -- the intersection of
69 # Allow the user to specify the BOLT targets, and then check that LLVM
80 message(STATUS "Targeting ${tgt} in llvm-bolt")
99 `--instrumentatio
[all...] |
| /llvm-project/lldb/docs/ |
| H A D | index.rst | 8 LLDB is a next generation, high-performance debugger. It is built as a set of
14 Objective-C and C++ on the desktop and iOS devices and simulator.
19 .. _"Apache 2.0 License with LLVM exceptions": https://llvm.org/docs/DeveloperPolicy.html#new-llvm-project-license-framework
22 ---
[all...] |
| /llvm-project/mlir/ |
| H A D | CMakeLists.txt | 11 # Check if MLIR is built as a standalone project.
38 # DLL platform -- put DLLs into bin.
43 set(LLVM_LIT_ARGS "-sv" CACHE STRING "Default options for lit")
67 # -BSymbolic is incompatible with TypeID
68 if("${CMAKE_SHARED_LINKER_FLAGS}" MATCHES "-Bsymbolic[^-]")
69 message(FATAL_ERROR " MLIR does not support `-Bsymbolic` (see http://llvm.org/pr51420 ),"
70 " try `-Bsymbolic-function
[all...] |