Flang Biweekly Sync - Notes from September 18th, 2019 call

Flang team,

Here are the notes from the September 18th, 2019 Flang biweekly call.

Please be sure to let us know if you have any questions and agenda topics for the next call.

The next Flang biweekly call will be Wednesday, October 2nd, 2019 at 8:30 AM Pacific Time.

The next Flang Technical Community call is Monday, September 23rd, 8:30 AM Pacific Time. The topic will be flangd, an example using f18 for tooling.

Thank you.

Gary Klimowicz

Agenda

  • SC 2019 – BoF for LLVM has been accepted
  • LLVM Developer Meeting news
  • MLIR for HPC Workshop news (at LCPC 2019)
  • Flang Community Technical Call – Recap and next topic: flangd
  • F18 development update
  • Flang development update

Highlights

  • Supercomputing 2019

  • The LLVM BoF session at SC 2019 was approved. No details yet about the schedule.

  • LLVM Developer Meeting 2019

  • The LLVM Dev Meeting is October 22-23 at the San Jose Convention Center; details can be found here.

  • Eric Schweitz’s talk, An MLIR Dialect for High-Level Optimization of Fortran, was accepted.

  • MLIR for HPC Workshop 2019

  • The MLIR for HPC workshop will be held October 21st in conjunction with the 32nd Workshop on Languages and Compilers for Parallel Computing October 22-24 at Georgia tech.

  • Flang Community Technical Biweekly Call

  • Hal Finkel is hosting this call on Bluejeans, Mondays 8:30 Pacific Time, on the weeks alternating with this call. The notes for all these calls can be found in Google Docs here. Note the new day.

  • On the September 9th call, we discussed module files, their content and format.

  • The next call is scheduled for Monday, September 23rd, 8:30 AM PDT. The agenda topic is flangd, an example using f18 for tooling.

  • F18 as an LLVM project

  • The LLVM-hosted flang-dev mailing list has been set up. Subscribe at https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev.

  • We have stopped using the original flang-dev@lists.flang-compiler.org and flang-sync@lists.flang-compiler.org. Further emails will be sent only to the LLVM lists.

  • F18 flang is still waiting to be added to the LLVM repo, but we are continuing to work with the LLVM admins; Hal is lending his support as well.

  • F18 update

  • “An MLIR Dialect for High-Level Optimization of Fortran” was accepted for the LLVM Developer Meeting.

  • Name resolution and semantics for Cray pointers.

  • More work on user procedure reference implementation design. Began semantic checks for calls.

  • More work on DO loop semantics and constraint checking.

  • Added a semantics stack for executable constructs.

  • OpenMP directive name resolution checking.

  • Began work on applying implicit types to names used in specification expressions.

  • MLIR has been proposed as an LLVM project. We continue to play catch-up with the changes to MLIR for f18.

  • The driver “flang” turns on semantic processing by default. This will make it easier for people to check existing codes against f18 and expanding the test suite in f18.

  • Arm Ltd generated a pull request for Clang as a first step for the new flang driver. The pull request for adding --fortran-mode can be found here: https://reviews.llvm.org/D63607.

  • Flang Dev news and updates

  • ICLA from Microsoft developer.

  • More bug fixes sent to Flang.

  • Work continues on the BLOCK construct.

  • Arm are now committers for flang-compiler/flang-driver.

  • License update to Apache 2.0 with LLVM exceptions is coming.

  • Working on LLVM 9 changes to Flang (differences between LLVM 8 and 9).

  • Decoupling PGI and Flang development to shorten turnaround on pull requests, add committers.

Where we can use your help

  • Subscribe to the new LLVM Flang email list: https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev. We will be cross-posting to both flang-dev mailing lists until September.
  • Topics for the next biweekly community call and technical community call.
  • Let us know if you have presentations or meetings relevant to the Flang community. We will publicize them in these notes.

**Details (**Updates are in bold)