[flang-dev] Flang Biweekly Sync - Notes from the April 29, 2020 call
Gary Klimowicz via flang-dev
flang-dev at lists.llvm.org
Fri May 1 08:33:26 PDT 2020
Flang team,
Here are the notes from the April 29th, 2020 Flang biweekly call.
The Flang Technical Community call was held Monday, April 20th, 8:30 AM Pacific Time. The next call will be Monday, May 4th.
The next Flang biweekly call will be Wednesday, May 13th, 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
* International Fortran conference
* LLVM Flang development update
* Original Flang development update
Highlights
* Slack invitation link updated
* If you had troubles joining flang-compiler.slack.com, try using the links in this email. They’ve been updated.
* 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/.
* LLVM Flang update
* Doxygen documentation support changes have been merged.
* Merged changes for MLIR and FIR; more to come. We are trying to balance the size of the commits against the fairly large amount of code that needs to be merged.
* Continued work on computing sizes and offsets of derived type components, COMMON and EQUIVALENCE.
* Continued work on lowering to FIR for control constructs (multiway branches, ASSIGN statements, alternate returns).
* Continued work on semantic checks for DATA statements (in review).
* Continued work on lowering DATA statements and array initializers.
* Arm continues work on OpenMP.
* A company may be interested in contributing a Fortran test suite to open source (not necessarily to LLVM).
* See the detailed notes below for other Flang development updates.
* Original Flang Dev news and updates
* We’ve added more external committers to Flang and are in the process of vetting and merging pull requests.
* Flang Community Technical Biweekly Call
* The last call was Monday, April 20th: IBM led a more detailed discussion about LLVM aliasing and Fortran. This discussion will continue on the flang-dev email list.
* The next technical call is scheduled for May 4th.
* Now what? 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.
Details (Updates below are in bold)
1. Flang on GitHub
· F18 has moved to https://github.com/llvm/llvm-project/tree/master/flang. There are 2350 commits in the flang/ tree.
· There have been 1,676 total commits to github.com/flang-compiler/flang (no change since the previous update).
· There are 526 people who have “starred” that flang repo and 74 forks.
1. Flang Community Technical Call (Hosted by Hal Finkel)
* The last call was April 20, 8:30 AM PT.
* IBM presented more detail about Fortran aliasing and proposed metadata changes to support Fortran semantics.
* The next call will be May 4, 8:30 AM PT.
* FIR and MLIR status and plan (Eric Schweitz, NVIDIA)
* Future Topics and tentative dates:
* Source-to-source translation (Craig Rasmussen and Kate Rasmussen; they have been looking at flang for Fortran source-to-source translation. This is in conjunction with the work to do semantic analysis and support of coarrays)
* 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. Add yourself via the invite <https://join.slack.com/t/flang-compiler/shared_invite/zt-2pcn51lh-VrRQL_YUOkxA_1CEfMGQhw> link.
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:
* Merged several changes for tests, Solaris.
* CMake support for generating doxygen file has been merged.
* Merged changes for MLIR and FIR; more to come. We are trying to balance the size of the commits against the fairly large amount of code that needs to be merged. We continue to follow the plan outlined in flang-dev http://lists.llvm.org/pipermail/flang-dev/2020-January/000162.html.
* Continued work on computing sizes and offsets of derived type components, COMMON and EQUIVALENCE.
* Continued work on semantic checking for TYPE (F2018 Clause 7). Phabricator reviews submitted for constraints C741-C750.
* Continued work on lowering to FIR for control constructs (multiway branches, ASSIGN statements, alternate returns).
* Continued work on semantic checks for DATA statements (in review).
* Continued work on lowering DATA statements and array initializers.
* Arm continues work on OpenMP.
* A company may be interested in contributing a Fortran test suite to open source (not necessarily to LLVM). There are discussions with ECP members.
1. What we’re up to with current Flang
* Added more committers to the Flang GitHub project. We will be working on pull requests in the stage branch.
* We have decoupled PGI and Flang development to shorten turnaround on pull requests and other development activity.
* Recent fixes pushed to Flang
* 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
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/flang-dev/attachments/20200501/f4659da4/attachment-0001.html>
More information about the flang-dev
mailing list