Home
last modified time | relevance | path

Searched +full:docs +full:- +full:libcxx +full:- +full:html (Results 1 – 25 of 42) sorted by relevance

12

/llvm-project/.github/workflows/
H A Ddocs.yml4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clan
[all...]
/llvm-project/llvm/utils/release/
H A Dbuild-docs.sh2 #===-- 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/
H A DREADME.md3 …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
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.
24 the [libc++ C++ standard library](https://libcxx.llvm.org),
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.
40 [LLVM Office Hours](https://llvm.org/docs/GettingInvolved.html#office-hours) or
[all …]
/llvm-project/libcxx/docs/
H A DREADME.txt7 To build the documents into html configure libc++ with the following cmake options:
9 * -DLLVM_ENABLE_SPHINX=ON
10 * -DLIBCXX_INCLUDE_DOCS=ON
12 After configuring libc++ with these options the make rule `docs-libcxx-html`
15 The documentation in this directory is published at https://libcxx.llvm.org. It is kept up-to-date
16 by a build bot: https://lab.llvm.org/buildbot/#/builders/publish-sphinx-docs. If you notice that the
H A DReleaseProcedure.rst8 `schedule <https://llvm.org/docs/HowToReleaseLLVM.html#annual-release-schedule>`__.
19 * Make sure ``libcxx/docs/ReleaseNotes/<VERSION>.rst`` is up to date. Typically
47 1. Update ``_LIBCPP_VERSION`` in ``libcxx/include/__config``
48 2. Update the version number in ``libcxx/docs/conf.py``
52 6. Point to the new release notes file from ``libcxx/docs/ReleaseNotes.rst``
60 available on `<https://apt.llvm.org>`_. Once it is available the pre-commit CI
67 The items that need changing are marked with ``LLVM POST-BRANCH``.
74 Support for the ToT - 3 version is removed:
76 - Search for ``LLVM RELEASE`` and address their comments
77 - Search for test that have ``UNSUPPORTED`` or ``XFAIL`` for the no longer supported version
[all …]
H A Dindex.rst19 * ABI compatibility with gcc's libstdc++ for some low-level features
70 Since its inception, libc++ has focused on delivering high performance, standards-conformance, and portability. It has
78 As an open-source project, libc++ benefits from a vibrant community of contributors who work together to improve the
84 -------
[all...]
H A DContributing.rst8 please also read `this document <https://www.llvm.org/docs/Contributing.html>`__ on general rules for
11 If you plan on contributing to libc++, it can be useful to join the ``#libcxx`` channel
14 Looking for pre-existing pull requests
19 filtering pull requests `tagged with libc++ <https://github.com/llvm/llvm-project/pulls?q=is%3Apr+is%3Aopen+label%3Alibc%2B%2B>`__.
23 RFCs for significant user-affecting changes
27 please consider creating a RFC on the `libc++ forum <https://discourse.llvm.org/c/runtimes/libcxx>`_.
49 ---
[all...]
H A Dconf.py1 # -*- coding: utf-8 -*-
21 # -- General configuration -----------------------------------------------------
37 # source_encoding = 'utf-8-sig'
44 copyright = "2011-%d, LLVM Project" % date.today().year
60 # non-false value, then it is used:
63 today_fmt = "%Y-%m-%d"
72 # If true, '()' will be appended to :func: etc. cross-reference text.
90 # -- Options for HTML output ---------------------------------------------------
92 # The theme to use for HTML and HTML Help pages. See the documentation for
96 # Theme options are theme-specific and customize the look and feel of a theme
[all …]
H A DModules.rst16 * `Clang specific modules <https://clang.llvm.org/docs/Modules.html>`_
17 * `C++ modules <https://clang.llvm.org/docs/StandardCPlusPlusModules.html>`_
51 * ``LIBCXX_ENABLE_EXCEPTIONS`` [#note-no-windows]_
57 .. [#note-no-windows] This configuration will probably not work on Windows
58 due to hard-coded compilation flags.
69 * The path to the compiler may not be a symlink, ``clang-scan-deps`` does
74 hard to solve and there is a work-around by first including all headers
75 `bug report <https://github.com/llvm/llvm-project/issues/61465>`__.
92 `bug report <https://github.com/llvm/llvm-project/issues/62943>`__.
118 .. code-block:: bash
[all …]
H A DTestingLibcxx.rst15 The primary way to run the libc++ tests is by using ``make check-cxx``.
24 .. _LIT Command Guide: https://llvm.org/docs/CommandGuide/lit.html
27 -----
30 running ``llvm-lit`` on a specified test or directory. If you're unsure
32 ``cxx-tes
[all...]
/llvm-project/clang/www/
H A Dhacking.html1 <!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...]
/llvm-project/libcxxabi/www/
H A Dindex.html1 <!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-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
20 <a href="/index.html">About</a>
25 <a href="https://libcxx.llvm.org/">libc++</a>
26 <a href="https://discourse.llvm.org/c/runtimes/libcxx/10">Discourse Forums</a>
27 <a href="https://lists.llvm.org/mailman/listinfo/libcxx-commits">libcxx-commits</a>
29 <a href="https://github.com/llvm/llvm-project/tree/main/libcxxabi/">Browse Sources</a>
34 <!--*********************************************************************-->
[all …]
/llvm-project/libcxx/docs/Helpers/
H A DReleaseNotesTemplate.rst2 Libc++ XX.YY.ZZ (In-Progress) Release Notes
9 Written by the `Libc++ Team <https://libcxx.llvm.org>`_
13 These are in-progress notes for the upcoming libc++ XX.YY.ZZ release.
15 `the Download Page <https://releases.llvm.org/download.html>`_.
24 documentation <https://llvm.org/docs/ReleaseNotes.html>`_. All LLVM releases may
28 <https://libcxx.llvm.org>`_ or the `LLVM Web Site <https://llvm.org>`_.
40 ------------------
44 -----------------------------
48 -------------------------
52 ----------------------------------
[all …]
/llvm-project/lldb/docs/resources/
H A Dbuild.rst5 ----------
[all...]
/llvm-project/libc/docs/
H A Dfull_host_build.rst19 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-project # The llvm-projec
[all...]
H A Dconf.py1 # -*- coding: utf-8 -*-
21 # -- General configuration ---
[all...]
/llvm-project/libcxx/docs/ReleaseNotes/
H A D19.rst2 Libc++ 19.0.0 (In-Progress) Release Notes
9 Written by the `Libc++ Team <https://libcxx.llvm.org>`_
13 These are in-progress notes for the upcoming libc++ 19.0.0 release.
15 `the Download Page <https://releases.llvm.org/download.html>`_.
24 documentation <https://llvm.org/docs/ReleaseNotes.html>`_. All LLVM releases may
28 <https://libcxx.llvm.org>`_ or the `LLVM Web Site <https://llvm.org>`_.
46 :ref:`pstl-status` for the current status.
49 `this issue <https://github.com/llvm/llvm-project/issues/99939>`__
53 -
[all...]
/llvm-project/libcxxabi/src/demangle/
H A DREADME.txt5 ----------
[all...]
/llvm-project/llvm/include/llvm/Demangle/
H A DREADME.txt5 ----------
[all...]
/llvm-project/llvm/docs/
H A DCMake.rst11 `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
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 DGettingStarted.rst19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This
21 -- and from there into object files, using LLVM.
24 the `libc++ C++ standard library <https://libcxx.llvm.org>`_,
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 DDiscourseMigrationGuide.md35 …to a category or topic](https://discourse.mozilla.org/t/how-do-i-subscribe-to-categories-and-topic…
37 ([tested](https://llvm.discourse.group/t/email-interaction-with-discourse/3306/4) on GMail).
38 …vious topics in an reply](https://meta.discourse.org/t/single-quote-block-dropped-in-email-reply/1…
40 `List-ID` email header field.
52 <tr><td>IR & Optimizations - Loop Optimizations</td><td>IR.Optimizations-Loops@discourse.llvm.org</…
54 <tr><td>Code Generation - AMDGPU</td><td>codegen-amdgpu@discourse.llvm.org</td></tr>
55 <tr><td>Code Generation - Common Infrastructure</td><td>codegen-common@discourse.llvm.org</td></tr>
56 <tr><td>Code Generation - AArch64</td><td>codegen-aarch64@discourse.llvm.org</td></tr>
57 <tr><td>Code Generation - Arm</td><td>codegen-arm@discourse.llvm.org</td></tr>
58 <tr><td>Code Generation - PowerPC</td><td>codegen-powerpc@discourse.llvm.org</td></tr>
[all …]
H A DReleaseProcess.rst17 -------------------------------
31 Not all bugs or regressions are show-stoppers and it's a bit of a grey area what
54 test-release.sh
55 ---------------
57 This script will check-out, configure and compile LLVM+Clang (+ most add-ons,
58 like ``compiler-rt``, ``libcxx``, ``libomp`` and ``clang-extra-tools``) in
61 directory, and that's the one you should use for the test-suite and other
66 ./test-release.sh \
67 -release 3.3 \
68 -rc 1 \
[all …]
/llvm-project/llvm/docs/Proposals/
H A DVariableNames.rst12 inevitably be some details that are flawed. You can help - you can edit this
15 <http://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html>`_.
26 <../CodingStandards.html#name-types-functions-variables-and-enumerators-properly>`_
43 The proliferation of acronyms leads to hard-to-read code such as `this
44 <https://github.com/llvm/llvm-project/blob/0a8bc14ad7f3209fe702d18e250194cd90188596/llvm/lib/Transf…
61 This work-in-progress proposal is to change the coding standard for variable
65 …<https://github.com/llvm/llvm-project/blob/8b72080d4d7b13072f371712eed333f987b7a18e/llvm/lib/CodeG…
74 but here we use the terminology from clang-tidy).
91 ------------------------------
114 While switching coding standard will make it easier to use non-acronym names for
[all …]
/llvm-project/clang/cmake/caches/
H A DCrossWinToARMLinux.cmake12 # --sysroot argument for specified target triple. Also it is possible
14 # -DCLANG_CONFIG_FILE_USER_DIR=<full-path-to-clang-configs>
16 # -DCLANG_CONFIG_FILE_SYSTEM_DIR=<full-path-t
[all...]

12