From: Tobias Burnus <burnus@net-b.de>
To: Martin Jambor <mjambor@suse.cz>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [wwwdocs] gcc-14/changes.html: OpenMP - improve wording
Date: Tue, 9 Jan 2024 17:48:19 +0100 [thread overview]
Message-ID: <f1749b1d-d95d-48ea-872f-7a0c06a29d83@net-b.de> (raw)
In-Reply-To: <ri6o7dufzdy.fsf@>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Ups - now attached. Thanks Martin!
Martin Jambor wrote:
> On Mon, Jan 08 2024, Tobias Burnus wrote:
>> The attached patch
>
> there was no patch attached to your message.
>
> Martin
>
>> does a tiny updated to the OpenMP features (AMD GCN
>> now also has an optimized memcpy_rect not only nvptx), but the main
>> change is some shifting around to make it more consistent and better
>> readable.
>>
>> I intend to commit this relatively soon; like always, comments and
>> suggestions are welcome - be it before or after the commit.
>>
>> Current version: http://gcc.gnu.org/gcc-14/changes.html
>>
>> Thanks,
>>
>> Tobias
[-- Attachment #2: improve-www.diff --]
[-- Type: text/x-patch, Size: 3927 bytes --]
gcc-14/changes.html: OpenMP - improve wording
This is mostly some shifting of items in bullet points to make it
more organized; it also improved the wording a bit. And there is one
new feature: the optimization for omp_target_memcpy_rect is now also
done for AMD GPUs and not only for nvptx.
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index e3a68998..2c64cf67 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -49,14 +49,24 @@ a work-in-progress.</p>
<ul>
<li id="openmp"><a href="https://gcc.gnu.org/projects/gomp/">OpenMP</a>
<ul>
+ <li>
+ The <a href="https://gcc.gnu.org/onlinedocs/libgomp/">GNU Offloading and
+ Multi Processing Runtime Library Manual</a> has been updated and extended,
+ improving especially the description of <abbr title="internal control
+ variables">ICVs</abbr>, memory allocation, environment variables and OpenMP
+ routines.
+ </li>
<li>
The <code>requires</code> directive's <code>unified_address</code>
requirement is now fulfilled by both AMD GCN and nvptx devices.
AMD GCN and nvptx devices now support low-latency allocators as
<a href="https://gcc.gnu.org/onlinedocs/libgomp/Offload-Target-Specifics.html"
>detailed in the manual</a>. Initial support for pinned-memory
- allocators has been added (<a href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html"
- >as detailed in the manual</a>)
+ allocators has been added and, on Linux,
+ <a href="https://github.com/numactl/numactl">libnuma</a> is now used
+ for allocators requesting the nearest-partition trait (both is described
+ in the <a href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html"
+ >memory allocation section of the manual</a>).
</li>
<li>OpenMP 5.0: The <code>allocate</code> directive is now
supported for stack variables in C and Fortran, including the OpenMP 5.1
@@ -74,8 +84,8 @@ a work-in-progress.</p>
using <code>present</code> as map-type modifier and in
<code>defaultmap</code>. The <code>indirect</code> clause is now supported
for C and C++. The performance of copying strided data from or to nvptx
- devices using the OpenMP 5.1 routine <code>omp_target_memcpy_rect</code>
- has been improved.
+ and AMD GPU devices using the OpenMP 5.1 routine
+ <code>omp_target_memcpy_rect</code> has been improved.
</li>
<li>
OpenMP 5.2: The <code>OMP_TARGET_OFFLOAD=mandatory</code> handling has
@@ -83,23 +93,14 @@ a work-in-progress.</p>
For Fortran, the list of directives permitted in Fortran pure procedures
was extended. Additionally, the spec change has been implemented for
default implicit mapping of C/C++ pointers pointing to unmapped storage.
- The <code>destroy</code> now optionally accepts the depend object as
- argument.
+ The <code>destroy</code> clause now optionally accepts the depend object
+ as argument.
</li>
<li>
OpenMP 6.0 preview (TR11/TR12): The <code>decl</code> attribute is now
supported in C++ 11 and the <code>directive</code>, <code>sequence</code>
and <code>decl</code> attributes are now supported in C 23.
</li>
- <li>
- The <a href="https://gcc.gnu.org/onlinedocs/libgomp/">GNU Offloading and
- Multi Processing Runtime Library Manual</a> has been updated and extended,
- improving especially the description of <abbr title="internal control
- variables">ICVs</abbr>, memory allocation, environment variables and OpenMP
- routines. On Linux, <a href="https://github.com/numactl/numactl">libnuma</a>
- is now used for allocators requesting the nearest-partition trait as
- detailed in the manual.
- </li>
</ul>
</li>
<li id="openacc"><a href="https://gcc.gnu.org/wiki/OpenACC">OpenACC</a>
prev parent reply other threads:[~2024-01-09 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:41 Tobias Burnus
2024-01-09 12:46 ` Martin Jambor
2024-01-09 16:48 ` Tobias Burnus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1749b1d-d95d-48ea-872f-7a0c06a29d83@net-b.de \
--to=burnus@net-b.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=mjambor@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).