commit | 8e6299a8885e46a67f568458654d341de55f4693 | [log] [tgz] |
---|---|---|
author | Tom Eccles <tom.eccles@arm.com> | Fri Apr 12 13:43:48 2024 +0100 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 12 05:50:36 2024 -0700 |
tree | d691d20f75d8a50ed8be907ffb2341c600e076a8 | |
parent | b3984160523d05847257300b97e731ee1d3d56f0 [diff] |
[flang][runtime] Add ACCESS library procedure (#88395) This is a GNU extension: https://gcc.gnu.org/onlinedocs/gfortran/ACCESS.html Used in SALMON: https://salmon-tddft.jp/download.html Unfortunately the intrinsic takes a file path to operate on so there isn't an easy way to make the test robust. The unit test expects to be able to create, set read write and execute permissions, and delete files called `std::filesystem::temp_directory_path() / <test_name>.<pid>` The test will fail if a file already exists with that name. I have not implemented the intrinsic on Windows because this is wrapping a POSIX system call and Windows doesn't support all of the permission bits tested by the intrinsic. I don't have a Windows machine easily available to check if Gfortran implements this intrinsic on Windows. GitOrigin-RevId: f220d26eb1ab5b588215acf538ca82bb3c8798cc
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.