[flang-dev] Flang Biweekly Sync - Notes from the June 10, 2020 call

[Gary Klimowicz via flang-dev]

Flang team,

Here are the notes from the June 10, 2020 Flang biweekly call.

The next Flang Technical Community will be Monday, June 15, 8:30 AM Pacific time. We will be discussing the RFC for refactoring front-end support for Clang and LLVM for Flang.

The next Flang biweekly call will be Wednesday, June 24, 2020 at 8:30 AM Pacific time.

Information for joining these calls and the Slack channel 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

  *   International Fortran Conference
  *   LLVM Technical Call topic
  *   Classic Flang pull request process update
  *   LLVM Flang development update

Highlights


  *   International Fortran Conference
     *   Ondřej Čertík (LFortran) and NVIDIA (Flang) have submitted abstracts. No word on acceptance yet.


  *   Flang Community Technical Biweekly Call
     *   Next topic: Outstanding reviews. Discuss the RFC for driver refactoring between LLVM and Clang to support a full Flang driver.
     *   The last call was June 1. Craig Rasmussen and Kate Rasmussen discussed experience with source-to-source translation using flang.
     *   Hal Finkel encourages people to add both small and large technical topics to the Google Doc for the technical call. The link to the Google Doc can be found in the notes below.


  *   LLVM Flang update
     *   Arm stood up a flang buildbot for Arm AArch64 at lab.llvm.org - see http://lab.llvm.org:8011/builders/flang-aarch64-ubuntu (GCC 9.3). They added another to build with Clang 8.
     *   NERSC and Argonne National Lab are working to set up buildbots as well. NERSC buildbot is in progress still.
     *   Andzrej Warzynski and Carol Concatto continue to work on the flang driver. Discussions continue on refactoring clang driver and LLVM utilities to better support multiple front ends.
     *   Continued work on semantic checking for TYPE (F2018 Clause 7). 63 of 115 checks are completed.
     *   Committee code for lowering I/O statement branching and loops in I/O data lists.
     *   Finished refactoring callee/caller interface lowering into a single utility based on the existing Fortran subprogram characteristics framework.
     *   Continued work on compiling all DATA statement initializations, including accounting for EQUIVALENCE and COMMON. This should wrap up this week.
     *   Continued work on MLIR and FIR in f18-llvm-project. Continued to push small commits to llvm-project for the fairly large amount of code that needs to be merged.


  *   Original Flang Dev news and updates
     *   We've pushed a simple change to the stage branch of flang.
     *   We will be publishing an RFC to flang-dev on handling the outstanding pull requests for classic Flang. Arm, AMD and NVIDIA(others are welcome!) will be evaluating the pull requests for merge into the master branch.


Details (Updates below are in bold)


  1.  Flang on GitHub
*         F18 has moved to https://github.com/llvm/llvm-project/tree/master/flang.
*         There have been 2392 commits for flang encompassing over 143,000 lines of code, documentation, CMakefiles and tests.
*         There have been 1,676 total commits to github.com/flang-compiler/flang (no change since the previous update).
*         There are 533 people who have "starred" that flang repo and 78 forks.



  1.  Flang Community Technical Call (Hosted by Hal Finkel)

  *   The last call was June 1. Craig Rasmussen and Kate Rasmussen discussed experience with source-to-source translation using flang.


  *   The next call will be Monday, June 15, 8:30 AM PT.
     *   Outstanding reviews
     *   Discussion of the RFC and incorporating feedback surrounding front-end support refactoring to allow Clang and Flang to share implementation.


  *   Future Topics and tentative dates:
     *   Build times for the compiler.
     *   Please feel free to add agenda topics to the Google Doc: https://docs.google.com/document/d/1Z2U5UAtJ-Dag5wlMaLaW1KRmNgENNAYynJqLW2j2AZQ/



  1.  Flang community

  *   Website: www.flang-compiler.org<http://www.flang-compiler.org> redirects to http://github.com/flang-compiler/flang.
  *   Wiki: https://github.com/flang-compiler/flang/wiki is the Flang wiki page where the most up-to-date build instructions and news can be found.


  *   Issues:
     *   Bug reports for LLVM flang should be reported in Bugzilla: https://bugs.llvm.org/. Use the "flang" tag for flang-related issues, please.
     *   Bug reports for current Flang can be reported to https://github.com/flang-compiler/flang/issues.


  *   LLVM mailing lists: There are now two mailing lists hosted by llvm.org:
     *   The flang-dev mailing list has been set up. Subscribe at https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev. These biweekly notes are now sent to this email list.
     *   The flang-commits mailing list has been set up. Subscribe at https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-commits.


  *   Slack: flang-compiler.slack.com is used for informal real-time communication in the Flang community. The invitation link can be found at the end of this email.


  *   International Fortran Conference
     *   FortranCon 2020 is the first International Conference targeting the development for and with the Fortran programming language and will take place on July 2 - 4 in Zurich, Switzerland.
     *   Virtual participation has always been part of their plan for the conference.
     *   The web site is at https://tcevents.chem.uzh.ch/event/12/.
     *   NVIDIA submitted an abstract for a talk on the status of Flang.
     *   Ondřej Čertík submitted an abstract for "LFortran: Interactive LLVM-based Fortran Compiler for Modern Architectures".
     *   The submission deadline for abstracts was June 1.



  1.  What we're up to with the llvm-project/flang Fortran 2018 compiler

  *   On GitHub: The source code LLVM Flang is available on https://github.com/llvm/llvm-project/tree/master/flang. It's recommended to start in the "documentation" directory.


  *   Public plan: The team maintains a plan for upcoming Flang work at https://github.com/orgs/flang-compiler/projects/. This reflects current LLVM Flang priorities and context for the project and its long-term goals.


  *   Status: We continue development. Recent work includes:

        *   Arm stood up a flang buildbot for Arm AArch64 at lab.llvm.org - see http://lab.llvm.org:8011/builders/flang-aarch64-ubuntu. They plan to add another.
        *   NERSC, LANL and Argonne National Lab are working to set up buildbots as well. NERSC buildbot is running, but failing; Brian Friesen is working through the issues. Argonne is working with ECP and security resources to negotiate whether they can set up their buildbot. LANL is facing the same uphill battle.
        *   Andzrej Warzynski and Carol Concatto continue to work on the flang driver. Discussions continue on refactoring clang driver and LLVM utilities to better support multiple front ends. (This triggered other discussions on refactoring, including ABI support and the use of MLIR for Clang. While important, the priority for Flang is getting a complete driver that doesn't depend on Clang.)

     *   Continued work on semantic checking for TYPE (F2018 Clause 7). 63 of 115 checks are completed.
     *   Committee code for lowering for I/O statement branching and loops in I/O data lists.
     *   Finished refactoring callee/caller interface lowering into a single utility based on the existing Fortran subprogram characteristics framework.
     *   Continued work on compiling all DATA statement initializations, including accounting for EQUIVALENCE and COMMON. This should wrap up this week.
     *   Continued work on MLIR and FIR in f18-llvm-project. Continued to push small commits to llvm-project for the fairly large amount of code that needs to be merged.





  1.  What we're up to with current Flang

     *   We pushed one pull requests to the stage branch. Continuing to work on a process for proposals, testing, approvals and merge.
     *   We are using the Slack channel #classic-flang-pull-requests to coordinate among the contributors.
     *   We are about to publish an RFC to flang-dev on the handling of pull requests for merge into Flang. This will involve multiple parties contributing to the testing effort for the pull requests.
     *   Recent fixes pushed to Flang stage
        *   #875<https://github.com/flang-compiler/flang/pull/875> Spelling fixes (a simple change)
     *   Recent fixes pushed to Flang master
        *   None

     *   Outstanding pull requests: https://github.com/flang-compiler/flang/pulls for the current list of pull requests.

     *   Outstanding issues: Please refer to the Issues section on GitHub for flang-compiler/flang<https://github.com/flang-compiler/flang/issues> and flang-compiler/flang-driver<https://github.com/flang-compiler/clang/issues>.


  *   OpenMP 4.5 support:
o    No update. OpenMP effort is now directed toward LLVM Flang.


  *   Debug Metadata:
     *   The outstanding review at https://reviews.llvm.org/D54114 [CHARACTER intrinsic data type] is stale and has been canceled. It will be replaced when there is an appropriate update for LLVM Flang.


  *   Packaging and Binary Releases:

  *   Spack: Spack packages for Flang have been updated. There is also a spack package for f18, based on the flang-compiler/f18 repository.


  *   Current Flang Fortran 2008 features
Current status of Fortran 2008 features can be found at https://github.com/flang-compiler/flang/wiki/Fortran-2008.



  1.  Logistics
Flang Community Biweekly Call

     *   General updates on the Flang project, both LLVM Flang and current Flang.
     *   Biweekly WebEx hosted by NVIDIA (which these notes cover).
     *   The meeting link for this biweekly call is https://nvmeet.webex.com/nvmeet/j.php?MTID=mb4edb8c799f69ec2dc0554acc969a162.

Note: If you are having difficulty connecting your audio, try using the "Call Me" option on WebEx to connect audio to your telephone.


Flang Community Technical Biweekly Call

     *   Technical topics call.
     *   Hal Finkel hosts this call on Bluejeans<https://bluejeans.com/625064848>, Mondays 8:30 Pacific Time, on the weeks alternating with regular Flang biweekly call. The notes for all these calls can be found in Google Docs here<https://docs.google.com/document/d/1Z2U5UAtJ-Dag5wlMaLaW1KRmNgENNAYynJqLW2j2AZQ/>.
Meeting URL: https://bluejeans.com/625064848?src=join_info
Meeting ID: 625 064 848
Want to dial in from a phone? Dial one of the following numbers:
+1.408.317.9254 (US (San Jose))
+1.866.226.4650 (US Toll Free)
(see all numbers - https://www.bluejeans.com/premium-numbers)
Enter the meeting ID and passcode followed by #
Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

Flang Slack Channel

     *   There is a Slack channel dedicated to Flang.
     *   Add yourself via the invitation link https://join.slack.com/t/flang-compiler/shared_invite/zt-2pcn51lh-VrRQL_YUOkxA_1CEfMGQhw

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/flang-dev/attachments/20200611/2eaa0ac2/attachment-0001.html>