[flang-commits] [flang] Add Flang Community Call Notes from June 17th meeting (PR #204622)

Thu Jun 18 08:32:36 PDT 2026

https://github.com/AlexisPerry created https://github.com/llvm/llvm-project/pull/204622

None

>From 21fa5736830e88e8569836f1ba47cecb5483289d Mon Sep 17 00:00:00 2001
From: AlexisPerry <aperry at lanl.gov>
Date: Thu, 18 Jun 2026 09:31:57 -0600
Subject: [PATCH] Add Flang Community Call Notes from June 17th meeting

---
 flang/docs/MeetingNotes/2026/2026-06-17.md | 73 ++++++++++++++++++++++
 1 file changed, 73 insertions(+)
 create mode 100644 flang/docs/MeetingNotes/2026/2026-06-17.md

diff --git a/flang/docs/MeetingNotes/2026/2026-06-17.md b/flang/docs/MeetingNotes/2026/2026-06-17.md
new file mode 100644
index 0000000000000..333871e925745
--- /dev/null
+++ b/flang/docs/MeetingNotes/2026/2026-06-17.md
@@ -0,0 +1,73 @@
+<!--===- docs/MeetingNotes/2026/2026-06-17.md
+
+   Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+   See https://llvm.org/LICENSE.txt for license information.
+   SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+
+-->
+# Community Call 2026-06-17
+
+## Agenda
+
+* Design docs and/or RFCs  
+  * [\[RFC\] Support for XRay in Flang](https://discourse.llvm.org/t/rfc-support-for-xray-in-flang/90987)   
+    * New contributor, please comment on Discourse post  
+  * [cpp-type.h: add HAS\_QUADMATHLIB to REAL(16) / CppFloat128Type guards](https://discourse.llvm.org/t/flang-cpp-type-h-add-has-quadmathlib-to-real-16-cppfloat128type-guards/91024)   
+    * Ongoing discussion on the post, please continue to comment to move the discussion forward  
+  * [\[RFC\]\[flang\]\[cmake\]\[perf-training\] Optimize flang with PGO and BOLT](https://discourse.llvm.org/t/rfc-flang-cmake-perf-training-optimize-flang-with-pgo-and-bolt/90884)  
+    * Related PRs:  
+      1. [\[flang\]\[cmake\]\[perf-training\] Optimize flang with PGO and BOLT by pawosm-arm · Pull Request \#197947 · llvm/llvm-project · GitHub](https://github.com/llvm/llvm-project/pull/197947)  
+      2. [\[flang\]\[cmake\]\[perf-training\] Optimize flang with PGO and BOLT by pawosm-arm · Pull Request \#198863 · llvm/llvm-project · GitHub](https://github.com/llvm/llvm-project/pull/198863)  
+    * One of the two PRs has been approved, after fruitful discussion.  Pawel would like to get one more approval before merging.  
+  * [\[RFC\] Support for \-std=f2023](https://discourse.llvm.org/t/rfc-support-for-std-f2023/89608)  
+    * Related PR: [\#196410 Generalize \-pedantic to take an optional argument](https://github.com/llvm/llvm-project/pull/196410)   
+      1. [\[RFC\] Support for \-std=f2023 \- Flang \- LLVM Discussion Forums](https://discourse.llvm.org/t/rfc-support-for-std-f2023/89608) Reviewers needed, as there are several different ways forward and detailed feedback is very much needed  
+    * Related Issue: [https://github.com/llvm/llvm-project/issues/196409](https://github.com/llvm/llvm-project/issues/196409)   
+    * Movement on the discussion has stalled, consensus has not been reached  
+    * If using \-pedantic=2023, the intention is for it to give a best effort to warn on all violations of the standard, not necessarily to be perfectly exhaustive  
+    * Tarun \- there doesn’t seem to be a great use of \-std= in the wild for Fortran codes  
+      1. Krzysztof \- there are uses of it, but the idea is to have uniformity across the LLVM ecosystem.  There seems to be a misunderstanding: \-std= as used in the Clang style as perceived in the Flang community seems to be stricter than it actually is  
+    * Chris Earl \- does using \-std=\<an older standard\> mean that all features from newer standards will be errors?  
+      1. Clang would accept the feature from a later standard and not warn unless \-pedantic was also passed (there are exceptions to this, but this approach is the general idea).  
+      2. As long as the feature does not contradict the standard being called on  
+    * Ted \- Would it be acceptable to proceed following the clang-style behavior and then tweak on a case-by-case basis?  
+      1. Tarun \- seems reasonable, as long as we have very clear documentation detailing the behavior so users do not expect stricter enforcement than we implement  
+    * Chris Earl \- in the specific case of SYSTEM\_CLOCK, should we leave the default behavior as is and only error if they use \-std=2023  
+      1. What about warning instead, and then if the user chooses to use \-Werror they will get the error  
+      2. Chris will make a PR for this  
+    * Ted \- Just for SYSTEM\_CLOCK, we should warn anytime a user uses the old behavior because it is a data corruption issue  
+      1. General agreement on the call that this is acceptable  
+  * [\[RFC\]\[flang\] Add Floating-point trap handling support](https://discourse.llvm.org/t/rfc-flang-add-floating-point-trap-handling-support/90544)   
+    * Github issue: [https://github.com/llvm/llvm-project/issues/198657](https://github.com/llvm/llvm-project/issues/198657)   
+  * [\[RFC\] Aggressive inlining for OpenMP SIMD loops](https://discourse.llvm.org/t/rfc-aggressive-inlinging-for-openmp-simd-loops/90558)   
+    * Needs more input from the community  
+  * [Changes to builtin modules](https://discourse.llvm.org/t/changes-to-builtin-modules/89072)   
+    * Has [broken apt.llvm.org packaging](https://github.com/llvm/llvm-project/issues/201304)  
+      1. Needs to be fixed by the maintainer, Michael Kruse has created an issue and tagged him
+
+* PRs of Note  
+  * *Reviewers needed:* [\[flang\]\[docs\] Extensions.md audit\#202331](https://github.com/llvm/llvm-project/pull/202331)   
+  * *Reviewers needed:* Fortran 2023 ENUMERATION TYPEs  
+    * Related to Issue [\#183789](https://github.com/llvm/llvm-project/issues/183789)   
+    * First PR in stack has been merged, continues here: [https://github.com/llvm/llvm-project/pull/193028](https://github.com/llvm/llvm-project/pull/193028)    
+  * *Reviewers needed:* Rank-1 integer arrays for explicit shape bounds  
+    * First PR in stack (3 total) has been merged, continues here:  
+      [https://github.com/llvm/llvm-project/pull/203030](https://github.com/llvm/llvm-project/pull/203030)  
+* Issues of Note
+
+* FYI  
+  * [LLVM Community Testimonial on Open Access](https://discourse.llvm.org/t/llvm-community-testimonial-on-open-access/91018)  
+  * Mark LeAir published a new flang update on the J3 site.  
+    * [https://j3-fortran.org/doc/year/26/26-175.txt](https://j3-fortran.org/doc/year/26/26-175.txt)  
+    * There is an updated version that includes OpenMP status: [https://j3-fortran.org/doc/year/26/26-175r1.txt](https://j3-fortran.org/doc/year/26/26-175r1.txt)  
+  * 2026 US LLVM Developers Meeting \- [Call for Proposals](https://discourse.llvm.org/t/2026-us-llvm-developers-meeting-call-for-proposals/91080)  
+    * Submit your proposal by July 14, 2026 (end of day AoE): [https://hotcrp.llvm.org/usllvm2026/](https://hotcrp.llvm.org/usllvm2026/)   
+  * [LLVM 22.1.8 Released\!](https://discourse.llvm.org/t/llvm-22-1-8-released/91084)   
+    * LLVM 23 will branch on Tuesday, July 14th
+
+* Other topics as time allows
+
+## Details
+
+* Consists of over **770,000** lines of code, documentation, build files, and test  
+* To date, over **12,532** commits have been made to Flang

