Thanks for proof reading and noting the missing patch …
Gerald Pfeifer:
On Tue, 29 Jul 2025, Tobias Burnus wrote:
Update https://gcc.gnu.org/gcc-16/changes.html for some OpenACC
features that went in; while small and some of them rather new
(OpenACC 3.4 was only released in June 2025), they all show up
in real-world code and, hence, are important to users.
Thumbs up.
Any comments before (or after) I pushed the changes?
-ENOPATCH?
Gerald
gcc-16/changes.html: Update OpenACC support
diff --git a/htdocs/gcc-16/changes.html b/htdocs/gcc-16/changes.html
index cc6fe204..a3148f6c 100644
--- a/htdocs/gcc-16/changes.html
+++ b/htdocs/gcc-16/changes.html
@@ -67,6 +67,18 @@ for general information.</p>
href="https://gcc.gnu.org/onlinedocs/libgomp/acc_005fmemcpy_005fdevice.html";>
<code>acc_memcpy_device</code> and <code>acc_memcpy_device_async</code></a>
API routines have been added for C, C++ and Fortran.</li>
+ <li>OpenACC 3.0: The <code>wait</code> directive now accepts the
+ <code>if</code> clause.</li>
+ <li>OpenACC 3.3: The Fortran API routines <code><a
+ href="https://gcc.gnu.org/onlinedocs/libgomp/acc_005fattach.html";>
+ acc_attach</a></code> and <code><a
+ href="https://gcc.gnu.org/onlinedocs/libgomp/acc_005fdetach.html";>
+ acc_detach</a></code> now augment their OpenACC 2.6 C/C++ counterparts.
+ </li>
+ <li>OpenACC 3.4: In Fortran, named constants (<code>PARAMETER</code>) used as
+ <em>var</em> in clauses are now accepted (and ignored as not being
+ required). The support for named constants has been added to the
+ specification and GCC for better compatibility with existing code.</li>
</ul>
<!-- <h3 id="ada">Ada</h3> -->
