|author||peter klausler <firstname.lastname@example.org>||Fri Jul 23 16:41:04 2021 -0700|
|committer||Copybara-Service <email@example.com>||Fri Jul 30 18:26:28 2021 -0700|
[flang] Produce proper "preprocessor output" for -E option Rename the current -E option to "-E -Xflang -fno-reformat". Add a new Parsing::EmitPreprocessedSource() routine to convert the cooked character stream output of the prescanner back to something more closely resembling output from a traditional preprocessor; call this new routine when -E appears. The new -E output is suitable for use as fixed form Fortran source to compilation by (one hopes) any Fortran compiler. If the original top-level source file had been free form source, the output will be suitable for use as free form source as well; otherwise there may be diagnostics about missing spaces if they were indeed absent in the original fixed form source. Unless the -P option appears, #line directives are interspersed with the output (but be advised, f18 will ignore these if presented with them in a later compilation). An effort has been made to preserve original alphabetic character case and source indentation. Add -P and -fno-reformat to the new drivers. Tweak test options to avoid confusion with prior -E output; use -fno-reformat where needed, but prefer to keep -E, sometimes in concert with -P, on most, updating expected results accordingly. Differential Revision: https://reviews.llvm.org/D106727 GitOrigin-RevId: 3338ef93b02837edf69abc203e15a42fa55aa1b3
Flang is a ground-up implementation of a Fortran front end written in modern C++. It started off as the f18 project (https://github.com/flang-compiler/f18) with an aim to replace the previous flang project (https://github.com/flang-compiler/flang) and address its various deficiencies. F18 was subsequently accepted into the LLVM project and rechristened as Flang.
Treatment of language extensions is covered in this document.
To understand the compilers handling of intrinsics, see the discussion of intrinsics.
To understand how a flang program communicates with libraries at runtime, see the discussion of runtime descriptors.
If you are interested in writing new documentation, follow markdown style guide from LLVM.
Flang is written in C++17.
The code has been compiled and tested with GCC versions from 7.2.0 to 9.3.0.
The code has been compiled and tested with clang version 7.0, 8.0, 9.0 and 10.0 using either GNU‘s libstdc++ or LLVM’s libc++.
The code has been compiled on AArch64, x86_64 and ppc64le servers with CentOS7, Ubuntu18.04, Rhel, MacOs, Mojave, XCode and Apple Clang version 10.0.1.
The code does not compile with Windows and a compiler that does not have support for C++17.
These instructions are for building Flang separately from LLVM; if you are building Flang alongside LLVM then follow the standard LLVM build instructions and add flang to
LLVM_ENABLE_PROJECTS instead, as detailed there.
The instructions to build LLVM can be found at https://llvm.org/docs/GettingStarted.html. If you are building flang as part of LLVM, follow those instructions and add flang to
We highly recommend using the same compiler to compile both llvm and flang.
The flang CMakeList.txt file uses
LLVM_DIRto find the installed LLVM components
MLIR_DIRto find the installed MLIR components
CLANG_DIRto find the installed Clang components
To get the correct LLVM, MLIR and Clang libraries included in your flang build, define
CLANG_DIR on the cmake command line.
LLVM=<LLVM_BUILD_DIR>/lib/cmake/llvm \ MLIR=<LLVM_BUILD_DIR>/lib/cmake/mlir \ CLANG=<LLVM_BUILD_DIR>/lib/cmake/clang \ cmake -DLLVM_DIR=$LLVM -DMLIR_DIR=$MLIR -DCLANG_DIR=$CLANG ...
LLVM_BUILD_DIR is the top-level directory where LLVM was built.
By default, cmake will search for g++ on your PATH. The g++ version must be one of the supported versions in order to build flang.
Or, cmake will use the variable CXX to find the C++ compiler. CXX should include the full path to the compiler or a name that will be found on your PATH, e.g. g++-8.3, assuming g++-8.3 is on your PATH.
CXX=/opt/gcc-8.3/bin/g++-8.3 cmake ...
To build flang with clang, cmake needs to know how to find clang++ and the GCC library and tools that were used to build clang++.
CXX should include the full path to clang++ or clang++ should be found on your PATH.
To specify a custom install location, add
-DCMAKE_INSTALL_PREFIX=<INSTALL_PREFIX> to the cmake command where
<INSTALL_PREFIX> is the path where flang should be installed.
To create a debug build, add
-DCMAKE_BUILD_TYPE=Debug to the cmake command. Debug builds execute slowly.
To create a release build, add
-DCMAKE_BUILD_TYPE=Release to the cmake command. Release builds execute quickly.
cd ~/flang/build cmake -DLLVM_DIR=$LLVM -DMLIR_DIR=$MLIR -DCLANG_DIR=$CLANG ~/flang/src make
The new Flang compiler driver,
flang-new, is implemented in terms of
clangDriver and hence it introduces a dependency on Clang. This dependency is otherwise not required. If you do not require the new driver, you can disable it by adding
-DFLANG_BUILD_NEW_DRIVER=OFF to your CMake invocation. With the new driver disabled, you no longer need to add
LLVM_ENABLE_PROJECTS (or to specify
CLANG_DIR when building out-of-tree).
Flang supports 2 different categories of tests
To run all tests:
cd ~/flang/build cmake -DLLVM_DIR=$LLVM -DMLIR_DIR=$MLIR ~/flang/src make test check-all
To run individual regression tests llvm-lit needs to know the lit configuration for flang. The parameters in charge of this are: flang_site_config and flang_config. And they can be set as shown below:
<path-to-llvm-lit>/llvm-lit \ --param flang_site_config=<path-to-flang-build>/test-lit/lit.site.cfg.py \ --param flang_config=<path-to-flang-build>/test-lit/lit.cfg.py \ <path-to-fortran-test>
If flang was built with
ON by default), it is possible to generate unittests. Note: Unit-tests will be skipped for LLVM install for an out-of-tree build as it does not include googletest related headers and libraries.
There are various ways to run unit-tests.
1. make check-flang-unit 2. make check-all or make check-flang 3. <path-to-llvm-lit>/llvm-lit \ test/Unit 4. Invoking tests from <out-of-tree flang build>/unittests/<respective unit test folder>
If flang was built with
On by default), it is possible to generate unittests.
To run all of the flang unit tests use the
To run all of the flang regression tests use the
If flang was built with
On by default), it is possible to generate FIR language documentation by running
make flang-doc. This will create
docs/Dialect/FIRLangRef.md in flang build directory.
To generate doxygen-style documentation from source code
-DLLVM_ENABLE_DOXYGEN=ON -DFLANG_INCLUDE_DOCS=ONto the cmake command.
cd ~/llvm-project/build cmake -DLLVM_ENABLE_DOXYGEN=ON -DFLANG_INCLUDE_DOCS=ON ../llvm make doxygen-flang
It will generate html in
<build-dir>/tools/flang/docs/doxygen/html # for flang docs
Flang documentation should preferably be written in
markdown(.md) syntax (they can be in
reStructuredText(.rst) format as well but markdown is recommended in first place), it is mostly meant to be processed by the Sphinx documentation generation system to create HTML pages which would be hosted on the webpage of flang and updated periodically.
If you would like to generate and view the HTML locally:
-DLLVM_ENABLE_SPHINX=ON -DSPHINX_WARNINGS_AS_ERRORS=OFFto the cmake command.
cd ~/llvm-project/build cmake -DLLVM_ENABLE_SPHINX=ON -DSPHINX_WARNINGS_AS_ERRORS=OFF ../llvm make docs-flang-html
It will generate html in