commit | 5274be9b49bfccc8610d96e74b157f49f6ae3c61 | [log] [tgz] |
---|---|---|
author | Valentin Clement (バレンタイン クレメン) <clementval@gmail.com> | Fri Apr 05 13:40:38 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 05 13:46:55 2024 -0700 |
tree | 9a8d498811b2f8cb7ddec1659485f571ba02f9c2 | |
parent | 276c0b5c89b7efc0c939d0fcac5439249e2c1c8e [diff] |
[flang][cuda] Add restriction on implicit data transfer (#87720) In section 3.4.2, some example of illegal data transfer using expression are given. One of it is when multiple device objects are part of an expression in the rhs. Current implementation allow a single device object in such case. This patch adds a similar restriction. GitOrigin-RevId: 0aa982fb326effa62277028375b5c346e0f6fcf5
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.