[flang-dev] Flang Biweekly Sync - Notes from the October 28, 2020 call

Gary Klimowicz via flang-dev flang-dev at lists.llvm.org
Thu Oct 29 15:08:26 PDT 2020


Flang team,

Here are the notes from the October 28, 2020 Flang Community biweekly call.

“LLVM Flang” is the Fortran 2018 compiler being developed as part of the LLVM project, and located in the LLVM monorepo (github.com/llvm/llvm-project).

“Classic Flang” is the original Flang Fortran 2003/2008 compiler located at github.com/flang-compiler/flang.

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

Upcoming calls (all times Pacific time):
Call
When
LLVM Flang Technical Community call
Monday, November 2, 8:30 AM
LLVM Alias Analysis call
Tuesday, November 3, 2020 at 10:00 AM
Classic Flang biweekly call
Wednesday, November 4, 2020 at 8:00 AM
(note time change)
OpenMP developer call
Thursday, November 5, 2020 at 8:00 AM
Flang biweekly call (this call)
Wednesday, November 11, 2020 at 8:30 AM

Information for joining these calls and the Flang Slack workspace is at the end of this email.

Thank you.

Gary


Agenda

  *   LLVM Flang Technical Call agenda
  *   LLVM Flang development update
  *   Classic Flang update

Highlights


  *   LLVM Flang Technical Call
     *   Monday’s call is likely to focus on the RFC to merge fir-dev.
     *   Discuss an update to the Flang line in the OpenMP support page.


  *   Flang Community Technical Biweekly Call
     *   Next call: November 2.
     *   Please 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.
     *   A new invitation has been sent by Johannes Doerfert.


  *   LLVM Flang updates

     *   Pat McCormick is preparing an RFC for upstreaming the fir-dev branch to the main LLVM branch
     *   More improvements for supporting Fortran 77 programs
     *   OpenACC semantic checks and lowering
     *   OpenMP semantic checks and lowering
     *   Began implementation of table-driven runtime for derived types
     *   Began implementation of array expression lowering
     *   More updates to flang driver
     *   We are now able to build and test on Windows with MSVC


  *   Classic Flang Dev news and updates
     *   At the previous meeting, Nick Romero reported that classic flang will be removed as a supported compiler from spack. He was handling many support requests for flang builds on Apple and requests for OpenMP target offload, which is slightly supported but not enough to develop programs.

Merged pull requests:

     *   #3<https://github.com/flang-compiler/classic-flang-llvm-project/pull/3>: Classic Flang monorepo: [DebugInfo] Support for DWARF 4/5 and fix of issues related to -gdwarf-X options
     *   #865<https://github.com/flang-compiler/flang/pull/865>: [DebugInfo]: Corrected emission of isOptimized flag
     *   #878<https://github.com/flang-compiler/flang/pull/878>: [DebugInfo]: Fix for missing DISPFlagOptimized in debug metadata
     *   #922<https://github.com/flang-compiler/flang/pull/922>: Fix private flag overwrite in find_def_in_most_recent_scope()
     *   #927<https://github.com/flang-compiler/flang/pull/927>: f90_correct: exclude tests failing with LLVM 10 on OpenPOWER
     *   #930<https://github.com/flang-compiler/flang/pull/930>: Fix HTML docs generation
     *   #931<https://github.com/flang-compiler/flang/pull/931>: [flang2] Fix segmentation faults (#421)
     *   #932<https://github.com/flang-compiler/flang/pull/932>: [flang1] Do not assume unempty derived types



Details (Updates below are in bold)


  1.  Flang on GitHub
·         LLVM Flang is in https://github.com/llvm/llvm-project/tree/master/flang.
·         There have been 2,7412 commits for LLVM Flang encompassing over 168,000 lines of code, documentation, CMakefiles and tests.
·         There have been 1,706 total commits to Classic Flang in github.com/flang-compiler/flang.
·         There are 549 people who have “starred” the Classic Flang repo and 83 forks.



  1.  Flang Community Technical Call (Hosted by Johannes Doerfert)

  *   The next technical community call topics:
     *   The RFC to merge fir-dev to LLVM upstream.
     *   Discuss an update to the Flang line in the OpenMP support page.


  *   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.  The LLVM alias analysis call was held Tuesday, October 6 as an LLVM Developers Meeting roundtable.

  *   The agenda document is at https://docs.google.com/document/d/1ybwEKDVtIbhIhK50qYtwKsL50K-NvB6LfuBsfepBZ9Y.



  1.  OpenMP Technical Call

  *   The call is held every Thursday at 8 am PDT/4 pm BST/8.30 pm IST to coordinate OpenMP work. The primary agenda item of the call is a development update from the engineers involved.
  *   Participants include AMD, Arm, the US National Labs and BSC.
  *   Kiran Kumar (email in CC) from AMD hosts the call. Please let him know if you plan to join and need an invite.


  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:

     *   Issues for LLVM flang should be reported in Bugzilla: https://bugs.llvm.org/. Use the “flang” tag for flang-related issues, please.
     *   Issues for Classic 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: subscribe at https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev. These biweekly notes are sent to this email list.
     *   The flang-commits mailing list: subscribe at https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-commits.


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



  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 “docs” 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. (OpenMP work for flang, clang ad OpenMPIR is tracked separately.)


  *   Status: We continue development. Recent work includes:

     *   More improvements for supporting Fortran 77 programs
     *   OpenACC semantic checks (wait, atomic directives)
     *   OpenACC lowering (lowering parallel, data constructs)
     *   OpenMP semantic checks for default clause
     *   OpenMP lowering for flush and ParallelOp clauses, including upstreaming from fir-dev
     *   Began implementation of table-driven runtime for derived types
     *   Began implementation of array expression lowering
     *   More updates to flang driver
     *   We are now able to build and test on Windows with MSVC
     *   Hal Finkel requested an updated plan on upstreaming fir-dev to the LLVM monorepo, now that we have Fortran 77 functionality in place; Pat McCormick is preparing an RFC




  1.  What we’re up to with Classic Flang

     *   We use the flang-compiler.slack.com channel #classic-flang-pull-requests to coordinate what pull requests we are working on.

     *   Recent fixes pushed to Classic Flang master
        *   #3<https://github.com/flang-compiler/classic-flang-llvm-project/pull/3>: Classic Flang monorepo: [DebugInfo] Support for DWARF 4/5 and fix of issues related to -gdwarf-X options
        *   #865<https://github.com/flang-compiler/flang/pull/865>: [DebugInfo]: Corrected emission of isOptimized flag
        *   #878<https://github.com/flang-compiler/flang/pull/878>: [DebugInfo]: Fix for missing DISPFlagOptimized in debug metadata
        *   #922<https://github.com/flang-compiler/flang/pull/922>: Fix private flag overwrite in find_def_in_most_recent_scope()
        *   #927<https://github.com/flang-compiler/flang/pull/927>: f90_correct: exclude tests failing with LLVM 10 on OpenPOWER
        *   #930<https://github.com/flang-compiler/flang/pull/930>: Fix HTML docs generation
        *   #931<https://github.com/flang-compiler/flang/pull/931>: [flang2] Fix segmentation faults (#421)
        *   #932<https://github.com/flang-compiler/flang/pull/932>: [flang1] Do not assume unempty derived types
     *   Pull requests in review:
        *   monorepo #5<https://github.com/flang-compiler/classic-flang-llvm-project/pull/5>: [Driver] Reduce downstream delta
        *   llvm mirror #87<https://github.com/flang-compiler/llvm/pull/87>: Enable github actions for llvm
        *   flang-driver #94<https://github.com/flang-compiler/flang-driver/pull/94>: Enable github actions
        *   #660<https://github.com/flang-compiler/flang/pull/660>: Enable support for simd directives
        *   #938<https://github.com/flang-compiler/flang/pull/938>: [flang2] Fixing possible crash due to ivl being NULL in dinit.cpp
        *   #907<https://github.com/flang-compiler/flang/pull/907>: [DebugInfo] flang produces dbg.declare and dbg.value for the same variable
        *   #908<https://github.com/flang-compiler/flang/pull/908>: [DebugInfo] Remove "_V_" from parameter names in case of byvalue parameters
        *   #933<https://github.com/flang-compiler/flang/pull/933>: Updating X-flag entries for internal command line option "-x 49"
        *   #938<https://github.com/flang-compiler/flang/pull/938>: [flang2] Fixing possible crash due to ivl being NULL in dinit.cpp
        *   #939<https://github.com/flang-compiler/flang/pull/939>: Publish Arm's internal documentation - part I
        *   #942<https://github.com/flang-compiler/flang/pull/942>: Implement UNROLL(n) directive (combines #742, #660)
     *   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>.
     *   Arm is planning to set up buildbots for Classic Flang. We should also set up OpenPOWER and x86 buildbots.


  *   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. From Nick Romero: “`spack install flang%gcc` and `spack install flang+cuda%gcc` build." Due to the number of questions he receives about building Classic Flang, it was decided in the last biweekly call to remove the Classic Flang Spack packages.


  *   Classic 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 (this call)

     *   General updates on the Flang project, both LLVM Flang and Classic 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.

Flang Community Technical Biweekly Call

     *   Technical topics call.
     *   Johannes Doerfert (ANL) 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

Classic Flang Biweekly Technical Call

     *   For people working on Classic Flang, the original Flang Fortran 2003/2008 compiler.
     *   The call is held every other Wednesday in the same week as the LLVM Flang Technical call (alternate week with the Flang Community Biweekly call).

The agenda is available here: https://docs.google.com/document/d/1-OuiKx4d7O6eLEJDBDKSRnSiUO2rgRR-c2Ga4AkrzOI.

Join the Microsoft Teams Meeting at https://teams.microsoft.com/l/meetup-join/19%3ameeting_YjM5YjlmNGEtMjA0MS00MTRlLTg5ZjUtOTM1ZGIxOTU2NWQy%40thread.v2<https://teams.microsoft.com/l/meetup-join/19%3ameeting_YjM5YjlmNGEtMjA0MS00MTRlLTg5ZjUtOTM1ZGIxOTU2NWQy%40thread.v2/0?context=%7b%22Tid%22%3a%22f34e5979-57d9-4aaa-ad4d-b122a662184d%22%2c%22Oid%22%3a%223641875c-ef5b-4767-8105-0787a195852f%22%7d>

+442033215213 (Toll)
Conference ID: 349 328 047#
Local numbers<https://dialin.teams.microsoft.com/7bdb65cd-97d0-44fe-bc03-bf8072eadc33?id=349328047>
Join with a video conferencing device
784150312 at t.plcm.vc<mailto:784150312 at t.plcm.vc> VTC Conference ID: 1220440737

LLVM Alias Analysis Technical Call

     *   For people working on improvements to LLVM alias analysis.
     *   Hal Finkel (?) hosts this call on Bluejeans<https://bluejeans.com/101176001>, Tuesdays 10:00 AM Pacific Time, every 4 weeks. The notes for all these calls can be found in Google Docs here<https://docs.google.com/document/d/1ybwEKDVtIbhIhK50qYtwKsL50K-NvB6LfuBsfepBZ9Y/>.
Meeting URL: https://bluejeans.com/101176001?src=join_info
Meeting ID: 101 176 001
Want to dial in from a phone? Dial one of the following numbers:
+1.312.216.0325 (US (Chicago))
+1.408.740.7256 (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

OpenMP Technical Call

·         Kiran Kumar T P (KiranKumar.TP at amd.com<mailto:KiranKumar.TP at amd.com>) from AMD hosts this weekly call on Microsoft Teams, Thursdays 8:00 AM Pacific time.

·         Please let Kiran know if you plan to join and need an invite.

o    Teams Call Link: https://bit.ly/39eQW3o

o    Minutes: https://docs.google.com/document/d/1yA-MeJf6RYY-ZXpdol0t7YoDoqtwAyBhFLr5thu5pFI

o    Project Management: https://docs.google.com/spreadsheets/d/1FvHPuSkGbl4mQZRAwCIndvQx9dQboffiD-xD0oqxgU0/<https://docs.google.com/spreadsheets/d/1FvHPuSkGbl4mQZRAwCIndvQx9dQboffiD-xD0oqxgU0/edit#gid=0>

Flang Slack Workspace

     *   There is a Slack workspace dedicated to Flang, flang-compiler.slack.com.
     *   There are a number of topic-oriented channels available (e.g., #driver, #f18-semantics, #f18-tooling, #fir).
     *   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/20201029/1902fd10/attachment-0001.html>


More information about the flang-dev mailing list