[flang-dev] Flang Biweekly Sync - Notes from the September 16, 2020 call
Gary Klimowicz via flang-dev
flang-dev at lists.llvm.org
Fri Sep 18 09:45:05 PDT 2020
Flang team,
Here are the notes from the September 16, 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, September 21, 8:30 AM
LLVM Alias Analysis call
Tuesday, October 6, 2020 at 10:00 AM
Classic Flang biweekly call
Wednesday, September 23, 2020 at 8:30 AM
OpenMP developer call
Thursday, September 24, 2020 at 8:00 AM
Flang biweekly call (this call)
Wednesday, September 30, 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 Virtual Developers’ Meeting
* LLVM Flang Technical Call agenda
* LLVM Flang development update
* Classic Flang update
Highlights
* LLVM Virtual Developers’ Meeting October 6-8
* http://llvm.org/devmtg/2020-09/
* Lightning talk: Valentin Clement: OpenACC support in Flang with a MLIR dialect (Wed October 7, 10:40 AM PT)
* Lightning talk: Steve Scalpone: Flang Update (Wed October 7, 12:00 PM PT)
* Technical talk: Johannes Doerfert: (OpenMP) Parallelism-Aware Optimizations (Thu October 8, 12:55 PM PT)
* Let me know of other talks to publicize here
* Flang Community Technical Biweekly Call
* Next call: September 21: Lowering array expressions to MLIR affine dialect (Rajan Walia)
* OpenACC 3.0 (Valentin Clement, ORNL)
* 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.
* LLVM Flang updates
* Andzrej Warzynski and Carol Concatto merged initial work on the flang driver
* More improvements for supporting Fortran 77 programs
* Improvements for distinguishing operators and assignment
* Continued work on lowering DO CONCURRENT control flow
* Began work on lowering COMMON and EQUIVALENCE with data initializations
* Began work on I/O for derived types using tables generated by semantics
* Updates for parsing OpenMP 5.0 atomic construct
* Updates for OpenMP allocate clause semantics
* More updates for Windows and MSVC
* Many documentation updates
·
* Classic Flang Dev news and updates
The following pull requests have been merged into Classic Flang:
* #737<https://github.com/flang-compiler/flang/pull/737>: TRAILZ function added to the fortran compiler
* #916<https://github.com/flang-compiler/flang/pull/916>: [runtime] Fix off-by-one error in minimum integers
The following pull requests are being reviewed:
* #1<https://github.com/flang-compiler/classic-flang-llvm-project/pull/1>: classic-flang-llvm-project: Port release_90 patches to LLVM 10 monorepo
* #888<https://github.com/flang-compiler/flang/pull/888>: flang gen-exec does not show routine variables with parameter attribute; there are multiple pull requests that this includes (details below)
* #919<https://github.com/flang-compiler/flang/pull/919>: Fix issue #670: Internal compiler error (from NVIDIA Fortran)
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,653 commits for LLVM Flang encompassing just under 164,000 lines of code, documentation, CMakefiles and tests.
· There have been 1,693 total commits to Classic Flang in github.com/flang-compiler/flang.
· There are 541 people who have “starred” the Classic Flang repo and 82 forks.
1. Flang Community Technical Call (Hosted by Hal Finkel)
* There was no call on September 7 (US Labor Day Holiday).
* The next technical community call will be Monday, September 21, 8:30 AM PT.
* Rajan Walia: MLIR lowering of array expressions with the affine dialect
* Valentin Clement: OpenACC 3.0
* 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, September 8.
* The agenda document is at https://docs.google.com/document/d/1ybwEKDVtIbhIhK50qYtwKsL50K-NvB6LfuBsfepBZ9Y.
* Status of the Full Restrict Patches (Joeren Dobbelaere has posted patches ready for review).
* Michael Kruse asked about a relationship between this provenance tracking and pointer comparison folding; there are notes from the discussion in the document.
* The next alias analysis call is scheduled for Tuesday, October 6. No specific agenda items yet.
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:
* Arm buildbots are set up at http://lab.llvm.org:8011/builders/flang-aarch64-ubuntu (GCC 9.3) and http://lab.llvm.org:8011/builders/flang-aarch64-ubuntu-clang (Clang 8). Two more coming with GCC 10 and Clang 10.
* NERSC buildbot is running in their staging area.
* IBM is setting up a buildbot (ppc64le-flang+mlir-rhel-test) for Flang + MLIR on Power + RHEL. The phabricator patch is available at https://reviews.llvm.org/D84956.
* Diana Pincus at Lenaro is setting up two build bots as well: Added flang to clang-cmake-aarch64-full.
* There was some discussion on setting up a mechanism to monitor performance changes in compile speed with each commit to LLVM flang (similar to what is done for LLVM and Clang)
* Andzrej Warzynski and Carol Concatto merged work on the flang driver
* More improvements for supporting Fortran 77 programs
* Improvements for distinguishing operators and assignment
* Began work on I/O for derived types using tables generated by semantics
* Continued work on lowering DO CONCURRENT control flow
* Began work on lowering COMMON and EQUIVALENCE with data initializations
* Preparing to upstream more work from fir-dev to LLVM master
* Many documentation updates
* Updates for parsing OpenMP 5.0 atomic construct
* Updates for OpenMP allocate clause semantics
* More updates for Windows and MSVC
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
* #737<https://github.com/flang-compiler/flang/pull/737>: TRAILZ function added to the fortran compiler
* #916<https://github.com/flang-compiler/flang/pull/916>: [runtime] Fix off-by-one error in minimum integers
* Pull requests in review:
* #1<https://github.com/flang-compiler/classic-flang-llvm-project/pull/1>: classic-flang-llvm-project: Port release_90 patches to LLVM 10 monorepo
* #888<https://github.com/flang-compiler/flang/pull/888>: flang gen-exec does not show routine variables with parameter attribute. There are multiple pull requests that this should be bundled with:
* #863<https://github.com/flang-compiler/flang/pull/863>: Support for -gdwarf-5 in flang2
* #921<https://github.com/flang-compiler/flang/pull/921>: Correction of representation of string (character type) constants
* Flang-driver #92<https://github.com/flang-compiler/flang-driver/pull/92>, #93<https://github.com/flang-compiler/flang-driver/pull/93>: Support for DWARF 4/5 and fix of issues related to -gdwarf-X options
* #919<https://github.com/flang-compiler/flang/pull/919>: Fix issue #670: Internal compiler error (from NVIDIA Fortran)
* 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.
* Debug Metadata:
* Several of the outstanding pull requests to merge into Classic Flang (above) are for debug metadata enhancements. These will be tracked in that section in future updates.
* 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, he will investigate using “master” as the default branch for Spack installs (and not the older labeled tags).
* 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.
* 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
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/20200918/e3680975/attachment-0001.html>
More information about the flang-dev
mailing list