commit | a19965d5bdb32fe54f7cca32ca8b46b14db7e3d3 | [log] [tgz] |
---|---|---|
author | Tom Eccles <tom.eccles@arm.com> | Fri Mar 08 10:33:43 2024 +0000 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 08 02:46:12 2024 -0800 |
tree | 3d72378b88138e1e20d7431d6b7c4c15541c94e6 | |
parent | c3be62e298a1789cfde9482c92d00f7d283e63a6 [diff] |
[flang][NFC] move loadIfRef to FIRBuilder (#84306) This will be useful for OpenMP too. I changed the definition slightly to use `fir::isa_ref_type` (which also includes llvm pointers) because I think it reads better using the common type helpers. There shouldn't be any llvm pointers in lowering so this isn't a functional change. GitOrigin-RevId: 860a40057da2fbb626fdf17feec18070d95b687b
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.