On 1/19/26 10:11, Tobias Burnus wrote:
The attached patch updates the OpenMP status in the GCC 16
release notes and is long overdue update. The current version
(or once committed: new version) can be found at:
https://gcc.gnu.org/gcc-16/changes.html
Comments? I intent to commit it tomorrow, but fixes can be
be also applied after I committed :-)
diff --git a/htdocs/gcc-16/changes.html b/htdocs/gcc-16/changes.html
index 052ef205..a83a3eca 100644
--- a/htdocs/gcc-16/changes.html
+++ b/htdocs/gcc-16/changes.html
@@ -49,6 +49,24 @@ a work-in-progress.</p>
</p>
<ul>
+ <li>The <a
href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html";>
+ memory allocation</a> support has been enhanced: for allocatators with
the
s/allocatators/allocators/
+ <code>pinned</code> trait, including
<code>ompx_gnu_pinned_mem_alloc</code>,
+ the <a href="https://gcc.gnu.org/onlinedocs/libgomp/nvptx.html";>CUDA
+ API (if available)</a> is used; this improves the performance when
accessing
+ this memory on Nvidia GPUs. The newly added
<code>ompx_gnu_managed_mem_alloc
+ </code>allocator and the <code>ompx_gnu_managed_mem_space</code> (both
GNU
This is a big garbled. Maybe
The newly-added <code>omp_gnu_managed_mem_alloc</code> and
<code>ompx_gnu_managed_mem_space</a> allocators ....
??
+ extensions) allocate device-accessible memory on the host. Such memory is
+ device accessible even when unified-shared memory is not supported and
+ might have different page-migration behavior on systems even if all host
+ memory is device accessible.
It's not clear to me what might have different page-migration behavior,
and what it is different from. :-S Can you try to rephrase this somehow?
+ <li>OpenMP 5.0: Limited support for <code>declare mapper</code> has
been added
+ for C and C++, only. The <code>uses_allocators</code> clause is now
+ supported, including the OpenMP 5.2 syntax changes and supporting
+ semicolons (OpenMP 6.0); for now, only predefined allocators are
supported.
+ <li>OpenMP 5.1: Initial support for the <code>iterator</code> modifier in map
+ clauses and the <code>target update</code> construct has been added for C
+ and C++.</li>
<li>OpenMP 5.2: The <code>begin declare variant</code> directive for C
and C++ is now supported.</li>
<li>OpenMP 6.0: The <a
@@ -56,7 +74,17 @@ a work-in-progress.</p>
<code>omp_target_memset</code></a> and <a
href="https://gcc.gnu.org/onlinedocs/libgomp/omp_005ftarget_005fmemset_005fasync.html";>
<code>omp_target_memset_async</code></a> API routines have been
- added.</li>
+ added. The <code>no_openmp_constructs</code> assumptions clause can now
+ be used.</li>
+ <li>OpenMP Technical Report 14 (TR14): The named
<code>omp_default_device</code>
+ constant has been added to denote the default-device number.</li>
+ <li>For OpenMP directives and clauses that have been deprecated in OpenMP
5.0,
+ 5.1, or 5.2, a deprecation warning shown, hinting at the to be used
syntax;
s/shown/is shown/
s/to be used/to-be-used/
-Sandra
