commit | 28d913f4aa8a006cf6edfb45dc5345ad876072fb | [log] [tgz] |
---|---|---|
author | Kareem Ergawy <kareem.ergawy@amd.com> | Wed Feb 28 13:02:23 2024 +0100 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 28 04:09:20 2024 -0800 |
tree | d0abac78f9bb2a08273d47bae23ea2e2a07ba604 | |
parent | 0735ab34f67bc6ed41622a001e3bc71d2e593710 [diff] |
[flang] Fix linker error for debug builds. (#83250) PR #81833 introduced some changes to broke some debug builds. This happened due to an indirectly included file referencing an `operator <<` function which is defined in a `.cpp` file that not linked with `tco` and `fir-opt`. GitOrigin-RevId: 2703f7ec4fb603a7c38288409c9ac919a47cca2a
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.