Flang Biweekly Sync - Notes from the April 15, 2020 call

Flang team,

Here are the notes from the April 15th, 2020 Flang biweekly call.

The Flang Technical Community call was held Monday, April 6th, 8:30 AM Pacific Time. The next call will be Monday, April 20th.

The next Flang biweekly call will be Wednesday, April 29th, 2020 at 8:30 AM Pacific Time.

Logistics information for these calls is at the end of this email.

Let me know if you have any topics you would like covered in the next call.

Thank you.

Gary Klimowicz

Agenda

  • Flang uploaded to LLVM!
  • Now what do we talk about on the next technical call?
  • F18 development update
  • Flang development update

Highlights

  • LLVM Flang update

  • Flang has been added to the LLVM monorepo. Many thanks to everyone who contributed to this effort.

  • The existing github.com/f18 repository has been marked as “moved to the monorepo”. Current pull requests against the f18 repository will need to migrate to LLVM repo and Phabricator.

  • IBM has published an RFC regarding aliasing information to flang-dev and llvm-dev.

  • See the detailed notes below for other Flang development updates.

  • Original Flang Dev news and updates

  • The parts of these call notes that change infrequently will refer to the Flang wiki for status. This will help us keep the Flang wiki up to date.

  • No update yet on the process for merging external contributions to Flang.

  • Flang Community Technical Biweekly Call

  • The last call was Monday, April 6th: We finalized the steps for the upload of Flang to the LLVM repository. There was also a brief discussion about LLVM aliasing and Fortran led by IBM. This discussion is continuing on the flang-dev email list.

  • The next technical call is scheduled for April 20th.

  • Now what? Hal Finkel encourages people to add both small and large technical topics to the Google Doc for the technical call. Now that we are past the hurdle of upstreaming the initial code base to LLVM, it’s time to talk more about real compiler issues! The link to the Google Doc can be found in the notes below.

**Details (**Updates below are in bold)