/llvm-project/polly/www/documentation/ |
H A D | passes.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-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 7 <title>Polly - The available LLVM passes</title> 13 <!--#include virtual="../menu.html.incl"--> 15 <!--*********************************************************************--> 17 <!--*********************************************************************--> 23 <li><em>polly-canonicalize</em> Prepare code for Polly</li> 24 <li><em>polly-detect</em> Detect SCoPs in functions</li> [all …]
|
/llvm-project/llvm/test/tools/llvm-cov/ |
H A D | multithreaded-report.test | 3 RUN: llvm-cov report -num-threads=1 \ 4 RUN: -path-equivalence=/tmp,%S/Inputs \ 5 RUN: -instr-profile %S/Inputs/multithreaded_report/main.profdata \ 8 RUN: llvm-cov report -num-threads=10 \ 9 RUN: -path-equivalence=/tmp,%S/Inputs \ 10 RUN: -instr-profile %S/Inputs/multithreaded_report/main.profdata \ 15 # Test "export" command with and without multiple threads. 16 RUN: llvm-cov export -num-threads=1 \ 17 RUN: -path-equivalence=/tmp,%S/Inputs \ 18 RUN: -instr-profile %S/Inputs/multithreaded_report/main.profdata \ [all …]
|
H A D | showLineExecutionCounts.cpp |
|
H A D | warnings.h | 1 …-cov show %S/Inputs/prevent_false_instantiations.covmapping -instr-profile %S/Inputs/elf_binary_co… 2 …-cov show %S/Inputs/prevent_false_instantiations.covmapping -instr-profile %S/Inputs/elf_binary_co… 3 …RUN: not llvm-cov report %S/Inputs/prevent_false_instantiations.covmapping -instr-profile %S/Input… 4 …RUN: not llvm-cov export %S/Inputs/prevent_false_instantiations.covmapping -instr-profile %S/Input… 6 // FAKE-FILE-STDOUT-NOT: warning: The file '{{.*}}' isn't covered. 7 // FAKE-FILE-STDERR: warning: The file '{{.*}}' isn't covered. 9 …-cov show %S/Inputs/prevent_false_instantiations.covmapping -instr-profile %S/Inputs/elf_binary_co… 10 …-cov show %S/Inputs/prevent_false_instantiations.covmapping -instr-profile %S/Inputs/elf_binary_co… 12 // FAKE-FUNC-STDOUT-NOT: warning: Could not read coverage for '{{.*}}'. 13 // FAKE-FUNC-STDERR: Could not read coverage for '{{.*}}'. [all …]
|
/llvm-project/clang-tools-extra/docs/ |
H A D | modularize.rst | 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 112 .. _module-map-coverage: 120 considers headers (no extension, .h, or .inc--if you need more, modify the 144 map coverage check, use the ``-coverage-check-onl [all...] |
H A D | clang-rename.rst |
|
/llvm-project/libcxx/docs/DesignDocs/ |
H A D | VisibilityMacros.rst | 8 .. _visibility-macros: 19 type_visibility to export RTTI and other type-specific information. Note that 21 type-specific attributes. The only exception are enums, which GCC always gives 38 overridden locally. On non-Windows, this is equivalent to `_LIBCPP_FUNC_VIS`. 56 by libc++ in v1 of the ABI, but that we don't want to export in the future. 75 **Windows Behavior**: DLLs do not support dllimport/export on class templates. 84 specified on the primary template and to export the member functions produced 95 regular import/export semantics, and applying `dllexport` directly to the 115 instantiations to export members, which is consistent with existing Windows 116 behavior. We also want classes annotated with `_LIBCPP_TYPE_VIS` to export [all …]
|
/llvm-project/lld/docs/ |
H A D | windows_support.rst | 1 .. raw:: html 4 .none { background-color: #FFCCCC } 5 .partial { background-color: #FFFF99 } 6 .good { background-color: #CCFF99 } 17 LLD supports Windows operating system. When invoked as ``lld-link.exe`` or with 18 ``-flavor link``, the driver for Windows operating system is used to parse 24 real-world binaries such as Firefox and Chromium. 35 export-by-name and export-by-ordinal are supported. 43 functions can be specified either via command line (``/EXPORT``) or via 44 module-definition file (.def). Both export-by-name and export-by-ordinal are [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. 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 46 the built files), install (holds the installed files, and compiler-rt (holds [all …]
|
/llvm-project/.github/workflows/ |
H A D | release-documentation.yml | 9 release-version: 20 release-version: 30 release-documentation: 32 runs-on: ubuntu-latest 34 upload: ${{ inputs.upload && !contains(inputs.release-version, 'rc') }} 36 - name: Checkout LLVM 39 - name: Setup Python env 40 uses: actions/setup-python@v5 43 cache-dependenc [all...] |
/llvm-project/llvm/docs/CommandGuide/ |
H A D | llvm-cov.rst | 1 llvm-cov - emit coverage information 4 .. program:: llvm-cov 7 -------- 9 :program:`llvm-cov` *command* [*args...*] 12 ----------- 14 The :program:`llvm-cov` tool shows code coverage information for 16 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation 20 the :program:`llvm-cov gcov` command were called. Otherwise, a command should 24 -------- 26 * :ref:`gcov <llvm-cov-gcov>` [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/llvm/tools/llvm-cov/ |
H A D | CodeCoverage.cpp | 1 //===- CodeCoverage.cpp - Coverage tool based on profiling instrumentation-===// 5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 //===--- 68 Export global() enumerator [all...] |
/llvm-project/llvm/utils/TableGen/ |
H A D | README.md | 17 ------------- Classes ----------------- 21 ------------- Defs ----------------- 35 * [TableGen Overview](https://llvm.org/docs/TableGen/index.html) 36 * [Programmer's reference guide](https://llvm.org/docs/TableGen/ProgRef.html) 38 … for Learning LLVM TableGen](https://blog.llvm.org/posts/2023-12-07-tools-for-learning-llvm-tableg… 40 …ive.fosdem.org/2019/schedule/event/llvm_tablegen/attachments/slides/3304/export/events/attachments… 42 …(video), [slides](https://llvm.org/devmtg/2019-10/slides/Absar-ImprovingYourTableGenDescription.pd… 45 * [TableGen Backend Developer's Guide](https://llvm.org/docs/TableGen/BackGuide.html) 46 * [How to write a TableGen backend](https://www.youtube.com/watch?v=UP-LBRbvI_U) 47 …(video), [slides](https://llvm.org/devmtg/2021-11/slides/2021-how-to-write-a-tablegen-backend.pdf)… [all …]
|
/llvm-project/third-party/benchmark/src/ |
H A D | CMakeLists.txt | 41 target_compile_definitions(benchmark PRIVATE -DHAVE_LIBPFM) 46 target_compile_definitions(benchmark PRIVATE -DBENCHMARK_HAS_PTHREAD_AFFINITY) 70 target_compile_definitions(benchmark PUBLIC -DBENCHMARK_STATIC_DEFINE) 109 export ( 119 EXPORT ${targets_export_name} 140 EXPORT "${targets_export_name}" 168 DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/html/"
|
/llvm-project/clang/docs/analyzer/user-docs/ |
H A D | CrossTranslationUnit.rst | 14 …be used in a variety of ways. The importing of external TU definitions can work with pre-dumped PCH 15 files or generating the necessary AST structure on-demand, during the analysis of the main TU. Driv… 18 …ted by other tools, like `CodeChecker <https://github.com/Ericsson/codechecker>`_ and scan-build-py 21 PCH-based analysis 26 `clang-extdef-mapping`. Entries in the index *must* have an `.ast` suffix if the goal 27 is to use PCH-based analysis, as the lack of that extension signals that the entry is to be used as… 37 .. code-block:: cpp 46 .. code-block:: cpp 55 .. code-block:: bash 60 "command": "clang++ -c foo.cpp -o foo.o", [all …]
|
/llvm-project/polly/docs/ |
H A D | UsingPollyWithClang.rst | 23 Optimizing with Polly is as easy as adding -O3 -mllvm -polly to your compiler 25 -O1,-O2,-O3; Optimizing for size with -Os or -Oz is not recommended). 27 .. code-block:: console 29 clang -O [all...] |
/llvm-project/mlir/lib/Target/LLVMIR/ |
H A D | ConvertToLLVMIR.cpp | 1 //===- ConvertToLLVMIR.cpp - MLIR to LLVM IR conversion -------------------===// 5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 //===----------------------------------------------------------------------===// 11 //===----------------------------------------------------------------------===// 17 #include "mlir/Target/LLVMIR/Export.h" 18 #include "mlir/Tools/mlir-translate/Translation.h" 30 "mlir-to-llvmir", "Translate MLIR to LLVMIR", in registerToLLVMIRTranslation() 39 // See https://llvm.org/docs/RemoveDIsDebugInfo.html in registerToLLVMIRTranslation() 43 llvmModule->removeDebugIntrinsicDeclarations(); in registerToLLVMIRTranslation() 44 llvmModule->print(output, nullptr); in registerToLLVMIRTranslation()
|
/llvm-project/clang/docs/ |
H A D | SourceBasedCodeCoverage.rst | 2 Source-based Code Coverage 11 This document explains how to use clang's source-based code coverage feature. 12 It's called "source-based" because it operates on AST and preprocessor 17 * :doc:`SanitizerCoverage` - A low-overhead tool meant for use alongside the 18 various sanitizers. It can provide up to edge-level coverage. 20 * gcov - A GCC-compatible coverage implementation which operates on DebugInfo. 21 This is enabled by ``-ftest-coverage`` or ``--coverage``. 23 From this point onwards "code coverage" will refer to the source-based kind. 36 The next few sections work through a complete, copy-'n-paste friendly example 39 .. code-block:: cpp [all …]
|
H A D | ClangPlugins.rst | 24 .. code-block:: c++ 29 if (args[i] == "-some-arg") { 42 .. code-block:: c++ 44 static FrontendPluginRegistry::Add<MyPlugin> X("my-plugin-name", "my plugin description"); 52 .. code-block:: c++ 72 .. code-block:: c++ 91 </doxygen/structclang_1_1ParsedAttrInfo_1_1Spelling.html>`_ of the 121 <https://github.com/llvm/llvm-projec [all...] |
/llvm-project/libcxx/include/__chrono/ |
H A D | tzdb_list.h | 1 // -*- C++ -*- 2 //===------ [all...] |
/llvm-project/llvm/docs/ |
H A D | ReleaseProcess.rst | 17 ------------------------------- 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 …]
|
H A D | HowToUpdateDebugInfo.rst | 27 ---------- [all...] |
/llvm-project/compiler-rt/lib/fuzzer/dataflow/ |
H A D | DataFlow.cpp | 1 /*===- DataFlow.cpp - a standalone DataFlow tracer -------===// 5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 //===----------------------------------------------------------------------===// 8 // An experimental data-flow tracer for fuzz targets. 10 // https://clang.llvm.org/docs/DataFlowSanitizer.html 11 // https://clang.llvm.org/docs/SanitizerCoverage.html#tracing-data-flow 17 // and also provides basic-block coverage for every input. 20 // 1. Compile this file (DataFlow.cpp) with -fsanitize=dataflow and -O2. 21 // 2. Compile DataFlowCallbacks.cpp with -O2 -fPIC. 22 // 3. Build the fuzz target with -g -fsanitize=dataflow [all …]
|
/llvm-project/clang/utils/analyzer/ |
H A D | SATestBuild.py | 12 - ProjectMap file 13 - Historical Performance Data 14 - Project Dir1 15 - ReferenceOutput 16 - Project Dir2 17 - ReferenceOutput 22 - Copy over a copy of the Repository Directory. (TODO: Prefer to ensure that 25 - Build all projects, until error. Produce logs to report errors. 26 - Compare results. 34 The compiler for scan-buil [all...] |