commit | 3c038d33e8cbf9bfa6cecd352d493e50417b390a | [log] [tgz] |
---|---|---|
author | Arthur Eubanks <aeubanks@google.com> | Wed Apr 10 23:41:51 2024 +0000 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 10 16:48:04 2024 -0700 |
tree | 327d5602da34431e42429853fb3d93e6ca3e4821 | |
parent | 0fb7623b0cc0481619a7c4312844d02c699d8009 [diff] |
Revert "[Driver] Ensure ToolChain::LibraryPaths is not empty for non-Darwin" This reverts commit ccdebbae4d77d3efc236af92c22941de5d437e01. Causes test failures in the presence of Android runtime libraries in resource-dir. See comments on https://github.com/llvm/llvm-project/pull/87866. GitOrigin-RevId: be10070f91b86a6f126d2451852242bfcb2cd366
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.