[flang-commits] [flang] [flang] Add notes from 10/21 Flang Community Call (PR #234268)

[Eugene Epshteyn via flang-commits]

================
@@ -0,0 +1,75 @@
+<!--===- docs/MeetingNotes/2026/2026-10-21.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-10-21
+
+## Agenda
+
+* Design docs and/or RFCs
+  * [\[RFC\] Relaxing coding standard rule for {}-initialization](https://discourse.llvm.org/t/rfc-relaxing-coding-standard-rule-for-initialization/92443)
+    * Some initial discussion on Discourse, current status is a suggestion from one person that the rule should be relaxed for auto, but further relaxation is still desired by others
+    * Appeal to not overgeneralize and consider individual cases
+    * Currently there is a divergence from the LLVM Coding Standards, and there is a question about whether this is really what the community wants
+    * Agree to relax auto now, but need further discussion on further relaxation
+      * Will make PR for the docs
+  * [RFC: Compiler directives defined by plugins](https://discourse.llvm.org/t/rfc-compiler-directives-defined-by-plugins/92431)
+    * Related PR: [https\://github.com/llvm/llvm-project/pull/228757](https://github.com/llvm/llvm-project/pull/228757)
+    * No update at this time, continue discussion on PR
+  * [\[RFC\]\[flang\] Version array-section loops when the runtime extent matches the declared extent](https://discourse.llvm.org/t/rfc-flang-version-array-section-loops-when-the-runtime-extent-matches-the-declared-extent/91956)
+    * Related Issue: [https\://github.com/llvm/llvm-project/issues/227442](https://github.com/llvm/llvm-project/issues/227442)
+    * PR stack beginning here: [https\://github.com/llvm/llvm-project/pull/231205](https://github.com/llvm/llvm-project/pull/231205)
+    * Both PRs have received approvals, plan to merge later today
+  * [Add design doc for inline runtime checks](https://github.com/llvm/llvm-project/pull/228502)
+    * PR has been merged
+  * [\[RFC\]\[flang\] Expanding array expressions and assignments at O0/-g](https://discourse.llvm.org/t/rfc-flang-expanding-array-expressions-and-assignments-at-o0-g/91971)
+    * Relates to the previous bullet point topic. Addressing slow performance in places.
+    * No update at this time
+  * [Cross-compilation of real(kind=16)](https://discourse.llvm.org/t/cross-compilation-of-real-kind-16/89161)
+    * PR has been posted: [https\://github.com/llvm/llvm-project/pull/221907](https://github.com/llvm/llvm-project/pull/221907)
+    * Please put comments on the PR, the author can not attend the calls due to timezone issues
+    * Discussion is ongoing on the PR, but responses are being received
+
+  *  [\[RFC\] Reduce \`ExternalFileUnit::Emit()\` call overhead for formatted sequential output](https://discourse.llvm.org/t/rfc-reduce-externalfileunit-emit-call-overhead-for-formatted-sequential-output/91674)
+
+    * Related PR has been posted, needs follow-up review: [https\://github.com/llvm/llvm-project/pull/222522](https://github.com/llvm/llvm-project/pull/222522)
+  * [\[flang\] Module files incorrectly expose implicitly recognized intrinsics · Issue \#219570](https://github.com/llvm/llvm-project/issues/219570) / Intrinsic accessibility depends on compilation layout
+    * Themos was able to post an inquiry to J3, awaiting response
+    * There is a separate bug regarding the order of statements, but need confirmation from J3 to resolve what the correct behavior is
+    * J3 is meeting this week, question about whether this topic is on the meeting agenda
+      * If need help with the mechanics of submitting a topic to J3, reach out to Damian Rouson or Dan Bonachea
+  * [\[RFC\] .mod by-reference dependencies recorded versus enforced in flang-new](https://discourse.llvm.org/t/rfc-mod-by-reference-dependencies-recorded-versus-enforced-in-flang-new/91745)
+    * Themos \- has some (potentially radical) ideas for how to address this.  Will consult with his colleagues and then comment on the RFC
+  * [\[RFC\] The Cost of Templates when Building Flang](https://discourse.llvm.org/t/rfc-the-cost-of-templates-when-building-flang/91197)
+    * New PR stack (second to last has been merged): [https\://github.com/llvm/llvm-project/pull/216958](https://github.com/llvm/llvm-project/pull/216958)  (merged)
----------------
eugeneepshteyn wrote:

"(second to last has been merged)" and the trailing "(merged)" say the same thing, and there is a double space before the second one. One of the two can go.


https://github.com/llvm/llvm-project/pull/234268