| /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 ---
28 https://llvm.org/docs/GettingStarted.html.
36 compiler-rt. Note that compiler-rt is only needed to access libraries that
39 includig GNU and clang. But building compiler-rt requres using the clang
40 compiler built in the initial part of the build.
43 cloned and built files. Under that root directory, clone the source code
[all …]
|
| H A D | Real16MathSupport.md | 1 <!--===- docs/Real16MathSupport.md
5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 -->
11 To support most `REAL(16)` (i.e. 128-bit float) math intrinsics Flang relies
12 on third-party libraries providing the implementation.
14 `-DFLANG_RUNTIME_F128_MATH_LIB=libquadmath` CMake option can be used
16 to GCC `libquadmath` library. A Flang driver built with this option
23 Testing shows that `libquadmath` versions before GCC-9.3.0 have
27 Care must be taken by the distributors of a Flang package built
|
| /llvm-project/mlir/docs/Dialects/ |
| H A D | LLVM.md | 3 This dialect maps [LLVM IR](https://llvm.org/docs/LangRef.html) into MLIR by
8 [intermediate representation of LLVM](https://llvm.org/docs/LangRef.html) and
25 thread-safe alternatives compatible with the rest of the infrastructure. The
31 IR modules use the built-in MLIR `ModuleOp` and support all its features. In
40 [same syntax](https://llvm.org/docs/LangRef.html#data-layout) as in LLVM IR and
45 llvm.target_triple = "aarch64-linux-android"} {
53 syntax similar to that of the built
[all...] |
| /llvm-project/lldb/docs/resources/ |
| H A D | fuzzing.rst | 5 --------
7 …>`_ for different components of LLDB. The fuzzers are built with `libFuzzer <https://llvm.org/docs…
10 --------------------
16 -DLLVM_USE_SANITIZER='Address' \
17 -DLLVM_USE_SANITIZE_COVERAGE=On \
18 -DCLANG_ENABLE_PROTO_FUZZER=ON
20 …zzer's sanitizer coverage is available here: `<https://llvm.org/docs/LibFuzzer.html#fuzzer-usage>`_
22 If you want to debug LLDB itself when you find a bug using the fuzzers, use the CMake option ``-DCM…
28 $ ninja lldb-target-fuzzer
29 $ ninja lldb-commandinterpreter-fuzzer
[all …]
|
| H A D | build.rst | 5 ----------
[all...] |
| /llvm-project/mlir/docs/Tools/ |
| H A D | MLIRLSP.md | 6 [LSP](https://microsoft.github.io/language-server-protocol/) IDE language
7 extensions for various MLIR-related languages. An LSP language extension is
14 ## MLIR LSP Language Server : `mlir-lsp-server`
17 in the form of the `mlir-lsp-server` tool. This tool interacts with the MLIR C++
22 `mlir-lsp-server`, like many other MLIR based tools, relies on having the
24 formats used in the textual .mlir files. The `mlir-lsp-server` found within the
26 Downstream and out-of-tree users will need to provide a custom
27 `mlir-lsp-server` executable that registers the entities that they are
28 interested in. The implementation of `mlir-lsp-server` is provided as a library,
33 #include "mlir/Tools/mlir-lsp-server/MlirLspServerMain.h"
[all …]
|
| /llvm-project/openmp/docs/ |
| H A D | SupportAndFAQ.rst | 4 Please do not hesitate to reach out to us on the `Discourse forums (Runtimes - OpenMP) <https://discourse.llvm.org/c/runtimes/openmp/35>`_ or join
11 -----
16 - Development updates on OpenMP (and OpenACC) in the LLVM Project, including Clang, optimization, and runtime work.
17 - Join `OpenMP in LLVM Technical Call <https://bluejeans.com/544112769//webrtc>`__.
18 - Time: Weekly call on every Wednesday 7:00 AM Pacific time.
19 - Meetin
[all...] |
| /llvm-project/llvm/docs/ |
| 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
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
52 - runs all of Clang and LLVM's lit tests, and
[all …]
|
| H A D | Docker.rst | 12 We currently provide Dockerfiles with ``debian12`` and ``nvidia-cuda`` base images.
17 ----
24 -----
[all...] |
| H A D | CMake.rst | 11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
34 We use here the command-line, non-interactive CMake interface.
45 .. code-block:: console
53 .. code-block:: console
70 components are built; see the `Frequently Used LLVM-related
76 .. code-block:: console
78 $ cmake -
[all...] |
| H A D | GitHub.rst | 1 .. _github-reviews:
10 `Source Code <https://github.com/llvm/llvm-project>`_,
11 `Releases <https://github.com/llvm/llvm-project/releases>`_,
12 `Issue Tracking <https://github.com/llvm/llvm-project/issues>`_., and
13 `Code Reviews <https://github.com/llvm/llvm-project/pulls>`_.
22 intended to be able to support "stacked" pull-request. Do not create any branches in the
23 llvm/llvm-project repository otherwise, please use a fork (see below). User branches that
24 aren't associated with a pull-request **will be deleted**.
32 Graphite will want to create branches under ``llvm/llvm-project`` rather than your
39 If you didn't do the above and Graphite created non-prefixe
[all...] |
| H A D | GitBisecting.rst | 11 has a mostly linear history, it has a few merge commits that added projects --
14 toplevel project that was developed out-of-tree and then merged later.
21 See https://git-scm.com/docs/git-bisect for a good overview. In summary:
23 .. code-block:: bash
36 being able to reset, do the usual ``git checkout -f main; git reset --hard
43 a large code base with just-built clang. This can take a long time, so it's
46 automatically. Writing the script can take 10-20 minutes, but it's almost
47 always worth it -- you can do something else while the bisect runs (such
50 Here's an example run script. It assumes that you're in ``llvm-project`` and
51 that you have a sibling ``llvm-build-project`` build directory where you
[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.
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-scm.com/docs/gi
[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...] |
| /llvm-project/third-party/benchmark/docs/ |
| H A D | python_bindings.md | 3 Python bindings are available as wheels on [PyPI](https://pypi.org/project/google-benchmark/) for i…
5 Currently, pre-built wheels exist for macOS (both ARM64 and Intel x86), Linux x86-64 and 64-bit Win…
6 Supported Python versions are Python 3.8 - 3.12.
11 python -m pip install --upgrade pip # for manylinux2014 support
12 python -m pip install google-benchmark
16 environment. See the [official Python documentation](https://docs.python.org/3/library/venv.html)
24 python3 -m venv venv --system-site-packages
27 # upgrade Python's system-wide packages
28 python -m pip install --upgrade pip build
30 python -m build
[all …]
|
| H A D | platform_specific_build_instructions.md | 5 When the library is built using GCC it is necessary to link with the pthread
9 can link to pthread by adding `-pthread` to your linker command. Note, you can
10 also use `-lpthread`, but there are potential issues with ordering of command
15 [`pthread_create()`](https://www.qnx.com/developers/docs/7.1/index.html#com.qnx.doc.neutrino.lib_re…
20 The `shlwapi` library (`-lshlwapi`) is required to support a call to `CPUInfo` which reads the regi…
43 See instructions for building with Visual Studio. Once built, right click on the solution and chang…
48 too (`-lkstat`).
|
| /llvm-project/mlir/docs/ |
| H A D | DataLayout.md | 20 Built-in types are handled specially to decrease the overall query cost.
21 Similarly, built-in `ModuleOp` supports data layouts without going through the
53 provides hooks for them to provide target- and type-specific checks. For
65 Data layout property queries can be performed on the special object --
66 `DataLayout` -- which can be created for the given scoping operation. These
88 considered an anti-pattern since it discards the cache after use. Because of
104 conceptually a collection of key-value pairs called data layout specification
130 corresponds to the C++ class of the given type, e.g., `IntegerType` for built-in
139 allows for type-specific "interpolation" behavior where a type class can compute
142 by taking that of the closest from above integer type with power-of-two
[all …]
|
| /llvm-project/compiler-rt/docs/ |
| H A D | BuildingCompilerRT.rst | 4 Building Compiler-RT
12 The instructions on this page are aimed at vendors who ship Compiler-RT as part of an
14 are a user merely trying to use Compiler-RT in your program, you most likely want to
22 brief explanation and LLVM-specific notes. For full documentation, check the
23 CMake docs or execute ``cmake --help-variable VARIABLE_NAME``.
32 "INSTALL" target is built.
35 The C++ compiler to use when building and testing Compiler-RT.
38 .. _compiler-rt-specific options:
40 Compiler-RT specific options
41 -----------------------
[all …]
|
| /llvm-project/clang/www/ |
| H A D | related.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">
12 <!--#include virtual="menu.html.incl"-->
16 <p>As Clang matures, more and more projects are being built atop the Clang
22 …<p>Please email <a href="get_involved.html">cfe-dev</a> if you have a Clang related project you wo…
42 <a href="https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/clang.md">
43 https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/clang.md</a>
55 <a href="https://wiki.debian.org/llvm-clang">
56 https://wiki.debian.org/llvm-clang</a>
[all …]
|
| /llvm-project/utils/bazel/ |
| H A D | README.md | 3 *Warning* The Bazel build is experimental and best-effort, supported in line
5 [LLVM's peripheral support tier](https://llvm.org/docs/SupportPolicy.html).
10 up-to-date is on the people who use the Bazel build.
12 [Bazel](https://bazel.build/) is a multi-language build system focused on
22 [proposal](https://github.com/llvm/llvm-www/blob/main/proposals/LP0002-BazelBuildConfiguration.md)
27 1. `git clone https://github.com/llvm/llvm-project.git; cd llvm-project` if
31 https://docs
[all...] |
| /llvm-project/llvm/tools/gold/ |
| H A D | README.txt | 8 See docs/GoldPlugin.html for complete build and usage instructions.
10 NOTE: libLTO and LLVMgold aren't built without PIC because they would fail
11 to link on x86-64 with a relocation error: PIC and non-PIC can't be combined.
12 As an alternative to passing --enable-pic, you can use 'make ENABLE_PIC=1' in
|
| /llvm-project/openmp/ |
| H A D | CMakeLists.txt | 31 "Enable -Werror flags to turn warnings into errors for supporting compilers.")
36 "Path where built OpenMP libraries should be installed.")
56 "Path where built openmp libraries should be installed.")
59 "Path where built OpenMP libraries should be installed.")
92 include(config-ix)
107 # 32-bit systems are not supported either.
153 add_subdirectory(docs)
155 # Now that we have seen all testsuites, create the check-openmp target.
|
| /llvm-project/libc/docs/gpu/ |
| H A D | using.rst | 27 ----------
[all...] |
| /llvm-project/clang/lib/Headers/ |
| H A D | __clang_cuda_builtin_vars.h | 1 /*===---- cuda_builtin_vars.h - CUDA built-in variables ---------------------===
5 * SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 *===-----------------------------------------------------------------------===
17 // The file implements built-in CUDA variables using __declspec(property).
18 // https://msdn.microsoft.com/en-us/library/yhfk0thd.aspx
19 // All read accesses of built-in variable fields get converted into calls to a
44 // also disallows taking address of special variables, so we disable address-of
112 // builtin to do so. According to PTX v4.2 docs 'to date, all target
|
| /llvm-project/libc/docs/ |
| H A D | full_host_build.rst | 18 the same system on which the libc is being built. First, we will explain how to
19 build for developing LLVM-libc, then we will explain how to build LLVM-libc as
26 Below is the list of commands for a simple recipe to build LLVM-libc for
35 ``gcc-multilib`` package creates this symlink, or you can do it manually with
37 ``sudo ln -s /usr/include/<HOST TRIPLE>/asm /usr/include/asm``
38 (your host triple will probably be similar to ``x86_64-linux-gnu``)
40 .. code-block:: sh
42 $> cd llvm-projec
[all...] |