Fortran newsletter: August 2020#
Welcome to the August 2020 edition of the monthly Fortran newsletter. The newsletter comes out on the first calendar day of every month and details Fortran news from the previous month.
We continued the work on the Fortran-lang website, including:
#116: updates to the Quickstart tutorial on loop control and syntax
#120: updated the Book section with a comprehensive list of books about Fortran
#121, #122, #127, #128: additional packages added to the Fortran-lang.org packages page
#117: Adding a Benchmarks section, a new dedicated repository was created at https://github.com/fortran-lang/benchmarks and many details have been discussed in issues there
Let us know if you have any suggestions for the website and its content. We welcome any new contributors to the website and the tutorials page in particular - see the contributor guide for how to get started.
Fortran Standard Library#
What’s new in the Fortran Standard Library:
#223: the structure of the Fortran Standard Library has been modified for clarity and ease of use. With these changes, both experimental and stable procedures will reside together in the same modules. The status of the procedures (experimental vs stable) are documented in the code, in the specs, and in the API docs
Main ongoing discussions:
Fortran Package Manager#
What’s new in fpm:
We created the fpm-registry repository, which serves as a registry of fpm-enabled Fortran packages. Please see the README there to learn how to contribute a package. For now, the registry is simply a list of fpm-enabled Fortran packages that you can use as a dependency in your
fpm.tomlfile. Soon, this registry will be used to generate detailed metadata that will be used by fpm to allow you to search for packages from the command-line, e.g.
fpm search <package>or similar.
#146: We discussed the design of the new Fortran implementation of fpm in a video call. We agreed on the need for an intermediate package model which will allow for clean separation of fpm frontends (user interface, parsing, and semantics) and fpm backends (fpm itself, CMake, Make, etc.).
#131, #132, #139, #140, #142, #145, #147, #148, #151: We merged several pull requests toward the Fortran fpm implementation. The Haskell implementation has moved to the
fpm/bootstrapdirectory, and the Fortran implementation is developed in
fpm/fpm. The Fortran fpm is, of course, an fpm package itself so it can be built by the Haskell fpm. Soon, it will be able to be build by itself.
fpm is still in very early development, and we need as much help as we can get. Here’s how you can help today:
Try to use it. Does it work? No? Let us know! Read the fpm packaging guide to learn how to build your package with fpm.
Browse the open issues and see if you can help implement any fixes or features.
Adapt your Fortran package for fpm.
Improve the documentation.
The short term goal of fpm is to make development and installation of Fortran packages with dependencies easier. Its long term goal is to build a rich and decentralized ecosystem of Fortran packages and create a healthy environment in which new open source Fortran projects are created and published with ease.
We created the benchmarks repository with the goal to design and implement a comprehensive set of benchmarks. The benchmarks will aim to compare the performance of various Fortran compilers, as well as the performance of canonical algorithms implemented in Fortran and different languages. If you’d like to contribute in any way, be it the design, implementation, or testing of benchmarks, please join the ongoing discussion here.
We’ve begun to evaluate pull requests and merge them into the original Flang compiler again. There is now a biweekly call to discuss issues and plans for Classic Flang. The next call will be Wednesday, August 12, 8:30 AM Pacific time. The notes from previous calls, upcoming agenda and a link to join the call can be found here.
In the last call, AMD reviewed their outstanding pull requests for Fortran debug metadata enhancements.
Work continues on LLVM Flang, concentrating on semantics, lowering and runtime sufficient to compile and run Fortran 77 programs. We are fixing bugs we find in running FCVS and other test suites that use F77.
We cominue upstreaming the lowering code from the fir-dev fork (MLIR-based Fortran IR) into the llvm-project repository. Arm is working on changes to support a driver program to replace the throwaway driver we currently have.
AMD has been contributing parser and semantic processing for OpenMP constructs like task wait, barrier and parallel constructs.
Changes have been made to default parse/unparse/compile processing to default to gfortran (not NVIDIA Fortran).
Valentin Clement has been committing initial changes for OpenACC support.
What’s new in LFortran:
The initial prototype C++ backend can translate Fortran’s
do concurrentto C++’s
LFortran has a Twitter account for latest updates: @lfortranorg
Work is progressing on the production version of LFortran that is written in C++
22 Merge Requests were merged and 4 issues fixed in July 2020. Some notable ones:
The short term goal is to get the C++ based production version of LFortran matching most of the features from the Python prototype version and make a public release. The long term goal is to build a modern Fortran compiler that works with any production code and allows it to run efficiently on modern hardware (CPUs and GPUs), both interactively and compiling to binaries, and provide the basis for other tools such as the Fortran to C++ translation, editor support, automatic documentation generation (and doctesting like in Python), automatic formatting and others.
FortranCon 2020 was held July 2 - 4. with many interesting talks. See the talk schedule here. All presentations have been recorded and will be soon made available online by the FortranCon organizers.
We had our third Fortran Monthly call on July 16. You can read watch the recording below:
As usual, subscribe to the mailing list and/or join the Discourse to stay tuned with the future meetings.
We thank everybody who contributed to fortran-lang in the past month by commenting in any of the four repositories: