[flang-commits] [flang] [flang] Add Flang Community Call notes for the August 12th meeting (PR #215853)

[Eugene Epshteyn via flang-commits]

================
@@ -0,0 +1,84 @@
+<!--===- docs/MeetingNotes/2026/2026-08-12.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-08-12
+
+## Agenda
+
+* Design docs and/or RFCs  
+  * [\[RFC\]\[flang\] Promote loop-invariant array-section reductions for vectorization](https://discourse.llvm.org/t/rfc-flang-promote-loop-invariant-array-section-reductions-for-vectorization/91499)  
+    * Feedback has been given and rework is necessary, will remove from the agenda for now until that rework is completed  
+  * [\[RFC\] \- Path Forward for \_FortranAAssignSimple Runtime Optimization](https://discourse.llvm.org/t/rfc-path-forward-for-fortranaassignsimple-runtime-optimization/91527)  
+    * Discussion ongoing on the Discourse post  
+  * [Perfectly-nesting fir.do\_loop nests (drop IV round-trip \+ sink final store): lowering or a pass?](https://discourse.llvm.org/t/perfectly-nesting-fir-do-loop-nests-drop-iv-round-trip-sink-final-store-lowering-or-a-pass/91532)  
+    * Discussion ongoing on the Discourse post  
+  *  [RFC: Add \`-finit-local=\` to Flang for Initializing Automatic Variables](https://discourse.llvm.org/t/rfc-add-finit-local-to-flang-for-initializing-automatic-variables/91545)    
+    * Flang does not currently have a way to handle initializing automatic variables, while most other compilers have some way to do this  
+    * This RFC seeks to add an option to fill the gap  
+    * The most common case is to initialize to zero, but there is another common case to initialize to a user-supplied special value, this RFC seeks to cover these most common cases in an easily maintainable way  
+    * Related existing PR (but only covers the initialization to zero case): [https://github.com/llvm/llvm-project/pull/159788](https://github.com/llvm/llvm-project/pull/159788)  
+      * Should coordinate with the author of this one  
+  * [\[RFC\]\[Flang\] Improving temporary and local array allocations \- unify StackArray/MemoryAllocation](https://discourse.llvm.org/t/rfc-flang-improving-temporary-and-local-array-allocations-unify-stackarray-memoryallocation/91353)	  
+    * 3 of 5 PRs in stack have been merged, these remain:  
+      * [\#210766 — \[flang\] Enable allocation-placement pass by default](https://github.com/llvm/llvm-project/pull/210766)  
+      * [\#210930 — \[flang\] Remove legacy stack-arrays and memory-allocation-opt passes](https://github.com/llvm/llvm-project/pull/210930)  
+    * Need to assess if there is a performance regression, there was at least one but it did not appear severe, Jean will investigate further when he returns from vacation  
+  * [\[RFC\] add support for collapsed io calls for implicit do loops](https://discourse.llvm.org/t/rfc-add-support-for-collapsed-io-calls-for-implicit-do-loops/91416)  
+    * Related PR: [https://github.com/llvm/llvm-project/pull/212646](https://github.com/llvm/llvm-project/pull/212646)   
+      * Needs more reviews  
+  * [\[RFC\]\[flang\] Add Floating-point trap handling support](https://discourse.llvm.org/t/rfc-flang-add-floating-point-trap-handling-support/90544)   
+    * Github issue has been closed: [https://github.com/llvm/llvm-project/issues/198657](https://github.com/llvm/llvm-project/issues/198657)   
+    * Related PR has been merged: [https://github.com/llvm/llvm-project/pull/208828](https://github.com/llvm/llvm-project/pull/208828)   
+    * will open more issues and related PRs for further IEEE arithmetic support (F2023 chapter 17\)  
----------------
eugeneepshteyn wrote:

Starts lowercase where the other bullets are capitalized: `will open` → `Will open`.

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