commit | 75b05029182d7059233af44981134962314c4950 | [log] [tgz] |
---|---|---|
author | Michael Klemm <michael.klemm@amd.com> | Thu Apr 11 10:18:34 2024 +0200 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 11 01:24:25 2024 -0700 |
tree | 2a5ff91a458a893d31f5e5315c479ef67342531e | |
parent | 3c038d33e8cbf9bfa6cecd352d493e50417b390a [diff] |
[flang] Do not create .f18.mod files for each compiled module (#85249) The default CMake scripts had a copy operation to copy a compiled `.mod` file to also be available with suffix `.f18.mod`. This seems no longer needed. Also updated ModFiles.md to point to `-module-suffix`. --------- Co-authored-by: Kiran Chandramohan <kiranchandramohan@gmail.com> GitOrigin-RevId: a1cd5e69544ad3e6a865f5e0593ac26195ccb4f7
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.
Please note that flang is not ready yet for production usage.
Read more about flang in the docs directory. Start with the compiler overview.
To better understand Fortran as a language and the specific grammar accepted by flang, read Fortran For C Programmers and flang's specifications of the Fortran grammar and the OpenMP grammar.
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're interested in contributing to the compiler, read the style guide and also review how flang uses modern C++ features.
If you are interested in writing new documentation, follow LLVM's Markdown style guide.
Consult the Getting Started with Flang for information on building and running flang.