| /llvm-project/llvm/docs/AMDGPUDwarfExtensionAllowLocationDescriptionOnTheDwarfExpressionStack/ |
| H A D | AMDGPUDwarfExtensionAllowLocationDescriptionOnTheDwarfExpressionStack.md | 1 # Allow Location Descriptions on the DWARF Expression Stack <!-- omit in toc -->
14 that allows both typed values and location descriptions to be manipulated on the
16 on the stack. In addition, the call frame information (CFI) is extended to
17 support the full generality of location descriptions. This is done in a manner
18 that is backwards compatible with DWARF 5. The extension involves changes to the
21 The extension permits operations to act on location descriptions in an
23 operations to be defined to address the requirements of heterogeneous devices as
29 rules. However, these resulted in the need for more operations that did not
31 corner cases that had to be defined. The observation was that numerous
37 describes heterogeneous devices and the features they have that are not addressed by DWARF 5.
[all …]
|
| /llvm-project/bolt/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| /llvm-project/polly/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the icon
[all...] |
| /llvm-project/flang/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| H A D | OpenACC-descriptor-management.md | 3 Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
9 # OpenACC dialect: Fortran descriptor management in the offload data environment
13 This document describes the details of the Fortran descriptor management during the offload execution using OpenACC.
15 LLVM Flang compiler uses an extended CFI descriptor data structure to represent some Fortran variables along with their characteristics in memory. For example, the descriptor is used to access dummy assumed shape arrays in a context of a subroutine where the arrays' bounds are not explicit but are rather passed to the subroutine via the descripto
[all...] |
| /llvm-project/openmp/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| /llvm-project/mlir/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| H A D | BytecodeFormat.md | 3 This document describes the MLIR bytecode format and its encoding.
7 older version of the format can be targetted.
9 That said, it is important to realize that the promises of the
10 bytecode format are made assuming immutable dialects: the format
14 A dialect can opt-in to handle its own versioning through the
15 `BytecodeDialectInterface`. Some hooks are exposed to the dialect
16 to allow managing a version encoded into the bytecode file. The
17 version is loaded lazily and allows to retrieve the versio
[all...] |
| /llvm-project/clang-tools-extra/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| /llvm-project/clang/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| H A D | PCHInternals.rst | 8 This document describes the design and implementation of Clang's precompiled
9 headers (PCH) and modules. If you are interested in the end-user view, please
10 see the :ref:`User's Manual <usersmanual-precompiled-headers>`.
15 The Clang compiler frontend, ``clang -cc1``, supports two command line options
18 To generate PCH files using ``clang -cc1``, use the option `-emit-pch`:
24 This option is transparently used by ``clang`` when generating PCH files. The
25 resulting PCH file contains the serialized form of the compiler's internal
26 representation after it has completed parsing and semantic analysis. The PCH
27 file can then be used as a prefix header with the `-include-pch`
38 the design of precompiled headers is entirely driven by performance concerns.
[all …]
|
| H A D | InternalsManual.rst | 11 This document describes some of the more important APIs and internal design
12 decisions made in the Clang C front-end. The purpose of this document is to
13 both capture some of this high level information and also describe some of the
15 Clang, not for end-users. The description below is categorized by libraries,
16 and does not describe any of the clients of the libraries.
21 The LLVM ``libSupport`` library provides many underlying libraries and
26 The Clang "Basic" Library
29 This library certainly needs a better name. The "basi
[all...] |
| /llvm-project/llvm/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
[all …]
|
| H A D | AMDGPUDwarfExtensionsForHeterogeneousDebugging.rst | 26 execute on multiple devices within the same native process. Devices could
30 The AMD [:ref:`AMD <amdgpu-dwarf-AMD>`] ROCm platform [:ref:`AMD-ROCm
31 <amdgpu-dwarf-AMD-ROCm>`] is an implementation of the industry standard for
32 heterogeneous computing devices defined by the Heterogeneous System Architecture
38 The LLVM compiler has upstream support for commercially available AMD GPU
39 hardware (AMDGPU) [:ref:`AMDGPU-LLVM <amdgpu-dwarf-AMDGPU-LLVM>`]. The open
42 also being added by third parties to the GCC [:ref:`GCC <amdgpu-dwarf-GCC>`]
43 compiler and the Perforce TotalView HPC Debugger [:ref:`Perforce-TotalView
48 been identified. The :ref:`amdgpu-dwarf-extensions` section gives an overview of
49 the extension
[all...] |
| H A D | DeveloperPolicy.rst | 13 This document contains the LLVM Developer Policy which defines the project's
14 policy towards developers and their contributions. The intent of this policy is
15 to eliminate miscommunication, rework, and confusion that might arise from the
16 distributed nature of LLVM's development. By stating the policy in clear terms,
21 This policy is also designed to accomplish the following objectives:
23 #. Attract both users and developers to the LLVM project.
27 #. Keep the top of tree as stable as possible.
29 #. Establish awareness of the project's :ref:`copyright, license, and patent
30 policies <copyright-license-patents>` with contributors to the projec
[all...] |
| H A D | StackMaps.rst | 12 In this document we refer to the "runtime" collectively as all
13 components that serve as the LLVM client, including the LLVM IR
16 A stack map records the location of ``live values`` at a particular
17 instruction address. These ``live values`` do not refer to all the
18 LLVM values live across the stack map. Instead, they are only the
19 values that the runtime requires to be live at this point. For
20 example, they may be the values the runtim
[all...] |
| /llvm-project/lldb/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
7 # The format is:
17 # This tag specifies the encoding used for all characters in the config file
18 # that follow. The default is UTF-8 which is also the encoding used for all
19 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
20 # iconv built into libc) for the transcoding. See
21 # http://www.gnu.org/software/libiconv for the list of possible encodings.
25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26 # by quotes) that should identify the project.
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
[all …]
|
| /llvm-project/openmp/runtime/doc/doxygen/ |
| H A D | config | 3 # This file describes the settings to be used by the documentation system
7 # The format is:
17 # This tag specifies the encoding used for all characters in the config file
18 # that follow. The default is UTF-8 which is also the encoding used for all
19 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
20 # iconv built into libc) for the transcoding. See
21 # http://www.gnu.org/software/libiconv for the list of possible encodings.
25 # The PROJECT_NAME tag is a single word (or sequence of words) that should
26 # identify the project. Note that if you do not use Doxywizard you need
27 # to put quotes around the project name if it contains spaces.
[all …]
|
| /llvm-project/llvm/docs/DirectX/ |
| H A D | DXContainer.rst | 14 The DirectX Container (DXContainer) file format is the binary file format for
15 compiled shaders targeting the DirectX runtime. The file format is also called
16 the DXIL Container or DXBC file format. Because the file format can be used to
17 include either DXIL or DXBC compiled shaders, the nomenclature in LLVM is simply
20 DirectX Container files are read by the compiler and associated tools as well as
21 the DirectX runtime, profiling tools and other users. This document serves as a
22 companion to the implementation in LLVM to more completely document the file
30 header, and some number of bytes of data after the header in a defined format.
32 DX Container data structures are encoded little-endian in the binary file.
34 The LLVM versions of all data structures described and/or referenced in this
[all …]
|
| /llvm-project/llvm/docs/TableGen/ |
| H A D | BackGuide.rst | 13 The purpose of TableGen is to generate complex output files based on
14 information from source files that are significantly easier to code than the
15 output files would be, and also easier to maintain and modify over time. The
17 which are then processed by TableGen. The internalized records are passed on
18 to various backends, which extract information from a subset of the records
20 for C++, but may be any type of file that the backend developer needs.
23 complete reference manual, but rather a guide to using the facilities
24 provided by TableGen for the backends. For a complete reference to the
25 various data structures and functions involved, see the primar
[all...] |
| /llvm-project/clang/lib/Headers/ |
| H A D | tmmintrin.h | 3 * Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
19 /* Define the default attributes for the functions in this file. */
36 /// Computes the absolute value of each of the packed 8-bit signed
37 /// integers in the source operand and stores the 8-bit unsigned integer
38 /// results in the destination.
42 /// This intrinsic corresponds to the \ in _mm_abs_pi8()
[all...] |
| /llvm-project/mlir/include/mlir/Interfaces/ |
| H A D | TilingInterface.td | 3 // Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
23 The intent of this interface is to separate the generation of the loop
24 structure (and constructs used for it) from the information needed from
25 the operation to be able to tile them. As a result an implementation of
26 the tiling algorithm (like `scf::tileUsingSCF`) can generate the inter-tile
27 loop structure, and call into the method
[all...] |
| /llvm-project/clang/include/clang/AST/ |
| H A D | ASTImporter.h | 3 // Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
9 // This file defines the ASTImporter class which imports AST nodes from one
51 // \brief Returns with a list of declarations started from the canonical decl
52 // then followed by subsequent decls in the translation unit.
53 // This gives a canonical list for each entry in the redecl chain.
54 // `Decl::redecls()` gives a list of decls which always start from the
55 // previous decl and the next item is actually the previous item in the orde
[all...] |
| /llvm-project/mlir/docs/Dialects/ |
| H A D | Transform.md | 10 of the IR using a different portion of the IR. It refers to the IR being
11 transformed as payload IR, and to the IR guiding the transformation as
14 The main use case for this dialect is orchestrating fine-grain transformations
17 size) in the payload IR, applying loop tiling to those and only those
18 operations, and then applying loop unrolling to the inner loops produced by the
19 previous transformations. As such, it is not intended as a replacement for the
[all...] |
| /llvm-project/llvm/lib/Support/rpmalloc/ |
| H A D | README.md | 14 The code should be easily portable to any platform with atomic operations and an mmap-style virtual…
16 …y is put in the public domain; you can redistribute it and/or modify it without any restrictions. …
19 …causing extra allocated memory overhead in the thread caches compared to these allocators. We also…
21 …l as memory overhead by comparing the virtual memory mapped with the number of bytes requested in …
29 The benchmark producing these numbers were run on an Ubuntu 16.10 machine with 8 logical cores (4 p…
31 Configuration of the thread and global caches can be important depending on your use pattern. See […
35 Before calling any other function in the API, you __MUST__ call the initialization function, either…
37 …ur use of the allocator, you __SHOULD__ call __rpmalloc_finalize__ in order to release caches and …
40 The easiest way to use the library is simply adding __rpmalloc.[h|c]__ to your project and compile …
42 __rpmalloc_initialize__ : Call at process start to initialize the allocator
[all …]
|