| /llvm-project/.github/workflows/ |
| H A D | docs.yml | 4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
[all...] |
| /llvm-project/llvm/utils/release/ |
| H A D | build-docs.sh | 2 #===-- build-docs.sh - Tag the LLVM release candidates ---------------------===#
6 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
8 #===------------------------------------------------------------------------===#
14 # * dnf install doxygen texlive-epstopdf ghostscript \
15 # ninja-build gcc-c++
16 # * pip install --user -r ./llvm/docs/requirements.txt
18 # * apt-get install doxygen \
19 # ninja-build graphviz texlive-font-utils
20 # * pip install --user -r ./llvm/docs/requirements.txt
21 #===------------------------------------------------------------------------===#
[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
[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 ---
28 https://llvm.org/docs/GettingStarted.html.
35 which it depends. These projects include mlir, clang, flang, openmp, and
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
44 into a directory called llvm-project. The build will also
[all …]
|
| H A D | FlangDriver.md | 1 <!--===- docs/FlangDriver.md
5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 -->
[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/ -->
4 <html>
6 <META http-equi
[all...] |
| H A D | menu.html.incl | 7 <label>Clang Info</label>
8 <a href="http://llvm.org/releases/download.html">Download</a>
9 <a href="/index.html">About</a>
10 <a href="/features.html">Features</a>
11 <a href="/related.html">Related Projects</a>
12 <a href="/docs/UsersManual.html">User's Manual</a>
13 <a href="/compatibility.html">Language Compatibility</a>
14 <a href="/docs/LanguageExtensions.html">Language Extensions</a>
15 <a href="/c_status.html">C Status</a>
16 <a href="/cxx_status.html">C++ Status</a>
[all …]
|
| H A D | get_started.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <html>
5 <META http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <title>Clang - Getting Started</title>
12 <!--#include virtual="menu.html.incl"-->
16 <h1>Getting Started: Building and Running Clang</h1>
18 <p>This page gives you the shortest path to checking out Clang and demos a few
20 If you like what you see, please consider <a href="get_involved.html">getting
21 involved</a> with the Clang community. If you run into problems, please file
22 bugs on <a href="https://github.com/llvm/llvm-project/issues">the LLVM bug tracker</a>.</p>
[all …]
|
| H A D | get_involved.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <html>
5 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
6 <title>Clang - Get Involved</title>
12 <!--#include virtual="menu.html.incl"-->
16 <h1>Getting Involved with the Clang Project</h1>
18 <p>Once you have <a href="get_started.html">checked out and built</a> clang and
26 See the <a href="hacking.html">hacking</a> document for information on how
31 <p>Clang is a subproject of the <a href="https://llvm.org">LLVM Project</a>
35 <li><a href="https://discourse.llvm.org/c/clang/6">Clang Frontend Discourse forum</a> -
[all …]
|
| H A D | OpenProjects.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <html>
5 <META http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <title>Clang - Ope
[all...] |
| /llvm-project/clang-tools-extra/docs/ |
| H A D | CMakeLists.txt | 26 set(CLANG_TOOLS_DOXYGEN_QCH_FILENAME "org.llvm.clang.qch" CACHE STRING
28 set(CLANG_TOOLS_DOXYGEN_QHP_NAMESPACE "org.llvm.clang" CACHE STRING
30 set(CLANG_TOOLS_DOXYGEN_QHP_CUST_FILTER_NAME "Clang ${CLANG_VERSION}" CACHE STRING
31 "See http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-filters")
32 set(CLANG_TOOLS_DOXYGEN_QHP_CUST_FILTER_ATTRS "Clang,${CLANG_VERSION}" CACHE STRING
33 "See http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes")
76 add_custom_target(doxygen-clang-tools
79 COMMENT "Generating clang doxygen documentation." VERBATIM)
80 set_target_properties(doxygen-clang-tools PROPERTIES FOLDER "Clang Tools Extra/Docs")
83 add_dependencies(doxygen doxygen-clang-tools)
[all …]
|
| H A D | README.txt | 1 ----------------------------------
2 Documentation in clang-tools-extra
3 ----------------------------------
5 To generate documentation in HTML format from files in clang-tools-extra/docs,
6 build the docs-clang-tools-html target.
9 doxygen-clang-tools target.
|
| H A D | modularize.rst | 30 1. Read `Getting Started with the LLVM System`_ and `Clang Tools
31 Documentation`_ for information on getting sources for LLVM, Clang, and
32 Clang Extra Tools.
36 right place the LLVM build will build Clang Extra Tools and their
45 .. _Getting Started with the LLVM System: https://llvm.org/docs/GettingStarted.html
46 .. _Building LLVM with CMake: https://llvm.org/docs/CMak
[all...] |
| H A D | clang-rename.rst | |
| /llvm-project/llvm/docs/ |
| H A D | README.txt | 8 system to create HTML pages which are hosted on <https://llvm.org/docs/> and
11 If you instead would like to generate and view the HTML locally, install
12 Sphinx <http://sphinx-doc.org/> and then do:
14 cd <build-dir>
15 cmake -DLLVM_ENABLE_SPHINX=true -DSPHINX_OUTPUT_HTML=true <src-dir>
16 make -j3 docs-llvm-html
17 $BROWSER <build-dir>/docs/html/index.html
20 `docs/Foo.rst` <-> `<build-dir>/docs//html/Foo.html` <-> `https://llvm.org/docs/Foo.html`.
30 Building the manpages is similar to building the HTML documentation. The
32 default (which is `html`). Sphinx then produces the man pages in the
[all …]
|
| H A D | TestSuiteGuide.md | 1 test-suite Guide
5 ---------
[all...] |
| H A D | GettingStarted.rst | 14 itself called "LLVM". This contains all of the tools, libraries, and header
16 object files. Tools include an assembler, disassembler, bitcode analyzer, and
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 -
886 .. _tools: global() target
[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.
36 #. `Download <http://www.cmake.org/cmake/resources/software.html>`_ and install
39 #. Open a shell. Your development tools must be reachable from this shell
45 .. code-block:: console
53 .. code-block:: console
70 components are built; see the `Frequently Used LLVM-related
76 .. code-bloc
[all...] |
| /llvm-project/ |
| H A D | README.md | 3 …ds.dev/projects/github.com/llvm/llvm-project/badge)](https://securityscorecards.dev/viewer/?uri=gi…
5 …-project/actions/workflows/libcxx-build-and-test.yaml/badge.svg?branch=main&event=schedule)](https…
10 construction of highly optimized compilers, optimizers, and run-time
14 itself called "LLVM". This contains all of the tools, libraries, and header
16 object files. Tools include an assembler, disassembler, bitcode analyzer, and
19 C-like languages use the [Clang](https://clang.llvm.org/) frontend. This
20 component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode
21 -- and from there into object files, using LLVM.
30 [Getting Started with LLVM](https://llvm.org/docs/GettingStarted.html#getting-the-source-code-and-b…
34 the [Contributing to LLVM](https://llvm.org/docs/Contributing.html) guide.
[all …]
|
| /llvm-project/openmp/docs/ |
| H A D | index.rst | 6 additions. Please post on the `Discourse forums (Runtimes -
19 OpenMP impacts various parts of the LLVM project, from the frontends (`Clang
20 <https://clang.llvm.org/docs/OpenMPSupport.html>`_ and Flang), through
21 middle-end :ref:`optimizations <llvm_openmp_optimizations>`, up to the
24 A high-level overview of OpenMP in LLVM can be found :doc:`here <design/Overview>`.
36 both Flang and Clang. For this purpose, LLVM's OpenMP runtimes are
37 being extended to serve as OpenACC runtimes. In some cases, Clang
50 LLVM, since `version 11 <https://releases.llvm.org/download.html#11.0.0>`_ (12 Oct
51 2020), has an :doc:`OpenMP-Aware optimization pass <optimizations/OpenMPOpt>`
55 In-depth discussion of the topic can be found :doc:`here <optimizations/Overview>`.
[all …]
|
| /llvm-project/third-party/benchmark/docs/ |
| H A D | AssemblyTests.md | 26 // CHECK-LABEL: test_add:
40 [LLVM's Filecheck](https://llvm.org/docs/CommandGuide/FileCheck.html)
50 bits of assembly. ([`CHECK-NEXT`](https://llvm.org/docs/CommandGuide/FileCheck.html#the-check-next-…
53 * The tests are compiled with `-O3 -g0`. So we're only testing the
56 * The assembly output is further cleaned up using `tools/strip_asm.py`.
61 `<build-directory>/test/<test-name>.s`
63 … supports using [`CHECK` prefixes](https://llvm.org/docs/CommandGuide/FileCheck.html#cmdoption-che…
65 The Benchmark tests use `CHECK-CLANG` and `CHECK-GNU` for lines that
66 are only expected to match Clang or GCC's output respectively. Normal
67 `CHECK` lines match against all compilers. (Note: `CHECK-NOT` and
[all …]
|
| /llvm-project/lldb/docs/resources/ |
| H A D | build.rst | 5 ----------
[all...] |
| /llvm-project/clang/docs/ |
| H A D | IntroductionToTheClangAST.rst | 2 Introduction to the Clang AST
5 This document gives a gentle introduction to the mysteries of the Clang
7 Clang, or use tools that work based on Clang's AST, like the AST
10 .. raw:: html
14 `Slides <https://llvm.org/devmtg/2013-04/klimek-slides.pdf>`_
19 Clang's AST is different from ASTs produced by some other compilers in
23 Clang's AST a good fit for refactoring tools.
25 Documentation for all Clang AST nodes is available via the generated
26 `Doxygen <https://clang.llvm.org/doxygen>`_. The doxygen online
28 make a search for clang and the AST node's class name usually turn up
[all …]
|
| H A D | LibFormat.rst | 6 on Clang. This documents describes the LibFormat interface and design as well
9 If you just want to use `clang-format` as a tool or integrated into an editor,
13 ------
19 ---------
23 .. code-block:: c++
31 formatting. A list of options can be found under :ref:`style-options`.
36 .. _style-options:
39 -------------
43 several style guides are hard-coded:
45 .. code-block:: c++
[all …]
|
| /llvm-project/mlir/docs/Tools/ |
| H A D | MLIRLSP.md | 5 This document describes the tools and utilities related to supporting
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,
[all …]
|