[flang-dev] Flang Biweekly Sync - Notes from the March 18 and April 1 2020 calls
Gary Klimowicz via flang-dev
flang-dev at lists.llvm.org
Thu Apr 9 08:06:53 PDT 2020
Flang team,
Here are the notes from the March 18th and April 1st 2020 Flang biweekly calls.
The Flang Technical Community call was held Monday, April 6th, 8:30 AM Pacific Time. We continued discussions about the status of the flang upload to the LLVM monorepo. The next call will be Monday, April 20th.
The next Flang biweekly call will be Wednesday, April 15th, 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
* Continue discussing merging process and status
* F18 development update
* Flang development update
Highlights
* Flang Community Technical Biweekly Call
* The last call was Monday, March 23rd: Status update on the process for uploading F18 to the LLVM monorepo.
* The next technical call is scheduled for April 6th. We will want to close on actions and dates for upstreaming Flang to LLVM.
* New Flang update
* We continue to work through items regarding Flang’s readiness to be merged into the LLVM monorepo. This was the bulk of today’s discussion.
* The upstreaming was not be ready for the March 23 target we had. We will discuss in the technical call remaining items and timing.
* Pat McCormick and David Truby’s CMake change merged.
* We are working through more feedback on changes from clang-format settings. Coming to consensus on this is very important.
* Pre-merge task status can be found here: https://github.com/orgs/flang-compiler/projects/8.
* We are planning to do the merge in early April.
* 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.
Where we can use your help
* Topics for the biweekly calls and technical community calls.
* Let us know if you have presentations or meetings relevant to the Flang community. We will publicize these in these notes.
Details (Updates below are in bold)
1. Flang on GitHub
· There have been 1,676 total commits (no change since the previous update).
· There are 520 people who have “starred” the flang repo and 72 forks.
· 231 people are following f18 in 46 forks. There have been 3,119 commits.
1. Flang Community Technical Call
* The call was March 23rd, 8:30 AM PT.
* LLVM transition (continuation of discussions about uploading flang to the GitHub monorepo).
* Craig and Kate will presented an overview of this work, answered questions, and solicited feedback.
* The next call will be April 6, 8:30 AM PT.
* LLVM transition (continuation of discussions about uploading flang to the GitHub monorepo).
* Future talk: Using flang in a source-to-source rewriting scheme (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.
* Future Topics and tentative dates:
* Potential topics for future calls include build times for the compiler and status updates on MLIR.
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 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/enQtMjExOTEyMzQ3MjIxLTZkMDNlODc2YjgxZDY1NTQ2YWJiZWVhOGU2YWY0NDNiOWY0ZjQzNjYyZTNlZjBlNjgxY2U1ZjFjMmY5NzIwMzA> link.
1. What we’re up to with new LLVM Flang Fortran 2018 compiler
* On GitHub: The source code f18 is available on flang-compiler.github.com/f18<https://github.com/flang-compiler/f18/>. It’s recommended to start in the “documentation” directory.
* Status: We continue development on the new Fortran 2018 front-end. Recent work includes:
* Continuing work on preparing flang for migration to the LLVM monorepo. We have a project area for the work to do at https://github.com/orgs/flang-compiler/projects/8.
* Merged PR#1027: Porting F18 tests to use LLVM lit without FileCheck.
* Merged PR#1047: Replace the use std::ostream with LLVM streams llvm::ostream.
* Merged PR#1032: Replace mmap with llvm::MemoryBuffer.
* Merged PR#945: Bump clang-format version and remove some differences from LLVM.
* Merged PR#1069 for Windows support.
* Reformat with latest clang-format and .clang-format.
* Merged changes for MLIR and FIR; more to come.
* Implemented analysis of expressions in DATA statement constants.
* Implemented semantics for ENTRY and SELECT CASE statements.
* Added definability checks for LHS of assignments.
* Continued implementation of Fortran run-time, including ALLOCATABLE and CHARACTER APIs.
* Continued work on lowering to FIR for control constructs (DO, IF, SELECT CASE).
* Continuing work on Clause 7 (Types) semantic checks.
1. What we’re up to with current Flang (no update)
* We will be opening up Flang to more committers soon. We are working on the approval process across the wider set of committers.
* 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:
* See https://github.com/flang-compiler/flang/pulls for the current list of pull requests.
* Public plan: NVIDIA has published a brief plan for upcoming Flang work at https://github.com/orgs/flang-compiler/projects/. This reflects current F18 priorities and to provide better context for the project and its long-term goals.
* Creating pull requests: Contributor license agreements are no longer be required for the current flang compiler. We are defining the process by which pull requests are validated and reviewed before merging into Flang.
* OpenMP 4.5 support:
o No update
* 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>.
* Debug Metadata:
* LLVM Debug metadata changes posted to LLVM Phabricator for review; responding to review comments. The last remaining pull request can be found at https://reviews.llvm.org/D54114 [CHARACTER intrinsic data type]. Review for this is not complete, and we would like to get additional comments or alternate proposals.
* Packaging and Binary Releases:
* Binary release: We try to post binary releases quarterly.
* Spack: Spack packages for Flang have been reviewed by the Spack team and pulled into Spack for flang_20180921. We are still working through issues with defining the spack package for flang. Brian Homerding and Nichols Romero are working on Spack changes for the LLVM and Flang for the LLVM Git monorepo.
1. Fortran 2008 features
Current status of Fortran 2008 features can be found at https://github.com/flang-compiler/flang/wiki/Fortran-2008.
1. Call 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
-----------------------------------------------------------------------------------
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/20200409/d8a6023d/attachment-0001.html>
More information about the flang-dev
mailing list