| commit | b21424ea8f669a0e3a0088578ae4141d1ad58e48 | [log] [tgz] |
|---|---|---|
| author | Tom Eccles <tom.eccles@arm.com> | Fri Mar 01 10:16:27 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 01 02:19:00 2024 -0800 |
| tree | 5c96e0f18ed0b7ef3e0baffcaacb717f07c3441f | |
| parent | d12222bb748a017e7f89d246763e3ec9d01e5615 [diff] |
[flang][HLFIR] Use GreedyPatternRewriter in LowerHLFIRIntrinsics (#83438) In #83253 @matthias-springer pointed out that LowerHLFIRIntrinsics.cpp should not be using rewrite patterns with the dialect conversion driver. The intention of this pass is to lower HLFIR intrinsic operations into FIR so it conceptually fits dialect conversion. However, dialect conversion is much stricter about changing types when replacing operations. This pass sometimes looses track of array bounds, resulting in replacements with operations with different but compatible types (expressions of the same rank and element types but with or without compile time known array bounds). This is difficult to accommodate with the dialect conversion driver and so I have changed to use the greedy pattern rewriter. There is a lot of test churn because the greedy pattern rewriter also performs canonicalization. GitOrigin-RevId: 44c0bdb402271522a17704b4a18c8bf5efb55c4f
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.