/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/**' 18 - 'clan [all...] |
/llvm-project/flang/docs/ |
H A D | CMakeLists.txt | 28 set(FLANG_DOXYGEN_QCH_FILENAME "org.llvm.flang.qch" CACHE STRING 30 set(FLANG_DOXYGEN_QHP_NAMESPACE "org.llvm.flang" CACHE STRING 32 set(FLANG_DOXYGEN_QHP_CUST_FILTER_NAME "FLANG ${FLANG_VERSION}" CACHE STRING 33 "See http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-filters") 34 set(FLANG_DOXYGEN_QHP_CUST_FILTER_ATTRS "FLANG,${FLANG_VERSION}" CACHE STRING 35 "See http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes") 78 add_custom_target(doxygen-flang 81 COMMENT "Generating flang doxygen documentation." VERBATIM) 82 set_target_properties(doxygen-flang PROPERTIES FOLDER "Flang/Docs") 84 add_dependencies(doxygen doxygen-flang) [all …]
|
H A D | GettingStarted.md | 1 <!--===- docs/GettingStarted.md 5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 --> 12 --- 14 --- 17 ## Building flang 18 There are two ways to build flang. The first method is to build it at the same 21 all of the projects on which flang depends. Then, after creating this base 22 build, only build the flang code itself. This is called building standalone. 28 https://llvm.org/docs/GettingStarted.html. [all …]
|
H A D | ReleaseNotes.md | 1 # Flang |version| (In-Progress) Release Notes 5 > These are in-progress notes for the upcoming LLVM |version| release. 7 > Page](https://releases.llvm.org/download.html). 11 This document contains the release notes for the Flang Fortran frontend, 13 describe the status of Flang in some detail, including major 16 documentation](https://llvm.org/docs/ReleaseNotes.html). All LLVM 29 ## Non-comprehensive list of changes in this release 35 ## Fortran Language Changes in Flang 44 Flang's documentation is located in the `flang/docs/` directory in the 47 If you have any questions or comments about Flang, please feel free to [all …]
|
H A D | DesignGuideline.md | 1 <!--===- docs/DesignGuideline.md 5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 --> 11 --- 13 --- 19 When working on a new feature in flang, some design document should 21 that need support in flang are listed in llvm github project 22 [Flang features to be implemented](https://github.com/orgs/llvm/projects/12). 33 The design document should be added to the `docs` folder as a markdown document, 35 Phabricator is the pre-requisite to submitting patches implementing new [all …]
|
H A D | FlangDriver.md | 1 <!--===- docs/FlangDriver.md 5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 --> [all...] |
H A D | conf.py | 1 # -*- coding: utf-8 -*- 2 # Flang documentation build configuration file. 18 # -- General configuration ----------------------------------------------------- 39 if not tags.has("builder-man"): 50 # source_encoding = 'utf-8-sig' 56 project = "Flang" 57 copyright = "2017-%d, The Flang Team" % date.today().year 75 # non-false value, then it is used: 87 # If true, '()' will be appended to :func: etc. cross-reference text. 105 # -- Options for HTML output --------------------------------------------------- [all …]
|
H A D | InternalProcedureTrampolines.md | 1 <!--===- docs/InternalProcedureTrampolines.md 5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 --> [all...] |
H A D | FortranLLVMTestSuite.md | 4 --- 6 --- 9 The [LLVM Test Suite](https://github.com/llvm/llvm-test-suite) is a 11 first-time users read through [LLVM Test Suite 12 Guide](https://llvm.org/docs/TestSuiteGuide.html) which describes the 15 ## Running the LLVM test-suite with Fortran 19 cmake -G "Ninja" -DCMAKE_C_COMPILER=<path to C compiler> \ 20 -DCMAKE_CXX_COMPILER=<path to C++ compiler> \ 21 -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \ 22 -DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \ [all …]
|
H A D | OptionComparison.md | 1 <!--===- docs/OptionComparison.md 5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 --> [all...] |
H A D | C++style.md | 1 <!--===- docs/C++style.md 5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 --> 9 # Flang C++ Style Guide 12 --- 14 --- 17 This document captures the style guide rules that are followed in the Flang codebase. 20 * Use *clang-format* 24 by means of clang-format. 26 * Otherwise, where [LLVM's C++ style guide](https://llvm.org/docs/CodingStandards.html#style-issues) [all …]
|
H A D | DebugGeneration.md | 8 in MLIR by way of MLIR attributes. Flang can leverage these MLIR attributes to 16 availability of the Classic Flang compiler. 19 By default, Flang will not generate any debug or linetable information. 22 -gline-tables-only, -g1 : Emit debug line number tables only 23 -g : Emit full debug info 32 - Details of the compiler (name and version and git hash). 33 - Language Standard. We can set it to Fortran95 for now and periodically 35 - Optimisation Level. 36 - Type of debug generated (linetable/full debug). 37 - Calling Convention: `DW_CC_normal` by default and `DW_CC_program` if it is [all …]
|
H A D | doxygen.cfg.in | 16 #--------------------------------------------------------------------------- 18 #--------------------------------------------------------------------------- 21 # that follow. The default is UTF-8 which is also the encoding used for all text 25 # The default value is: UTF-8. 27 DOXYFILE_ENCODING = UTF-8 30 # double-quotes, unless you are using Doxywizard) that should identify the 35 PROJECT_NAME = "FLANG" 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 77 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), 79 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), [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/openmp/docs/ |
H A D | index.rst | 6 additions. Please post on the `Discourse forums (Runtimes - 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 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>`. 67 <https://llvm.org/docs/Remarks.html>`_ issues during 69 in various formats `[3]`_ `[4]`_ to be used by tools, i.a., `opt-viewer` or [all …]
|
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 | TestSuiteGuide.md | 1 test-suite Guide 5 --------- [all...] |
H A D | GettingInvolved.rst | 31 The LLVM project's code-review process. 34 The LLVM support policy for core and non-core components. 52 Describes how to use the llvm-project repository and code reviews on GitHub. 60 .. _development-process: 63 ------ [all...] |
H A D | DiscourseMigrationGuide.md | 35 …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 …]
|
/llvm-project/flang/docs/FIR/ |
H A D | CreateFIRLangRef.py | 1 # This script combines FIRLangRef_Header.md with the auto-generated Dialect/FIRLangRef.md 2 # for the purpose of creating an introduction header/paragraph for FIRLangRef.html. 6 # These paths are relative to flang/docs in the build directory, not source, as that's where this t… 11 # 1. Writes line 1 from docs to output, (comment line that the file is autogenerated) 14 # 4. Writes the remainder of docs to the output file 16 with open(HEADER_PATH, "r") as header, open(DOCS_PATH, "r") as docs: 17 output.write(docs.readline()) 20 output.write(docs.read())
|
/llvm-project/flang/ |
H A D | .clang-format | 1 --- 2 # See: https://clang.llvm.org/docs/ClangFormatStyleOptions.html 11 - Regex: '^<' 13 - Regex: '^"(llvm|llvm-c|clang|clang-c)/' 15 - Regex: '^"(flang|\.\.)/' 17 - Regex: '.*'
|
/llvm-project/mlir/include/mlir/Dialect/ArmSME/Transforms/ |
H A D | Passes.td | 1 //===-- Passes.td - ArmSME pass definition file ------- [all...] |
/llvm-project/openmp/ |
H A D | README.rst | 5 and Clang need a more recent version which also applies for in-tree builds. For 7 `LLVM's CMake documentation <https://llvm.org/docs/CMake.html>`_ and the 8 `official documentation <https://cmake.org/cmake/help/v2.8.0/cmake.html>`_. 15 - When calling CMake for the first time, all needed compiler options must be 20 - Example of configuring, building, reconfiguring, rebuilding: 22 .. code-block:: console 26 $ cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ .. # Initial configuration 30 $ cmake -DCMAKE_BUILD_TYPE=Debug .. # Second configuration 33 $ rm -rf * 34 $ cmake -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ .. # Third configuration [all …]
|
/llvm-project/flang/include/flang/Optimizer/CodeGen/ |
H A D | Target.h | 1 //===- Target.h - target specific details -------- [all...] |
/llvm-project/llvm/ |
H A D | CMakeLists.txt | 1 # See docs/CMake.html for instructions about how to build LLVM with CMake. 30 # "Symbol version prefix for libLLVM.so and libclang-cpp.so" 36 "default, even for 64-bit targets. This can result in linker " 37 "instability and out of memory errors. To use the 64-bit " 38 "host compiler, pass -Thost=x64 on the CMake command line.") 91 No build type selected. You need to pass -DCMAKE_BUILD_TYPE=<type> in order to configure LLVM. 93 * -DCMAKE_BUILD_TYPE=Release - For an optimized build with no assertions or debug info. 94 * -DCMAKE_BUILD_TYP [all...] |