From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Andrew Stubbs <andrew_stubbs@mentor.com>,
Julian Brown <julian@codesourcery.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: [wwwdocs] gcc-12/changes.html: GCN - add TI mode, mention -foffload(-options)
Date: Tue, 29 Jun 2021 17:34:00 +0200 [thread overview]
Message-ID: <bc65b173-eaa4-5c49-d5bd-ba82013c86ea@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
This documents AMD GCN's new much-more complete TI-mode
(__int128_t) support, that was as v2 just posted by Julian
and should get committed very soon.
Additionally, -foffload= (previously undocumented) has been
split into -foffload= and -foffload-options= and now has a
documentation. Hence, both flags are now in the release notes,
linking to their documentation. (Link are broken until the
next cron run.)
Comments? Concerns? Remarks?
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf
[-- Attachment #2: wwdocs.diff --]
[-- Type: text/x-patch, Size: 1171 bytes --]
gcc-12/changes.html: GCN - add TI mode, mention -foffload(-options)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index b854c4e6..599443e7 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -62,6 +62,14 @@ a work-in-progress.</p>
OpenACC. It warns about potentially suboptimal choices related to
OpenACC parallelism.
</li>
+ <li>The offload target code generation for OpenMP and OpenACC can now
+ be better adjused using the new <a
+ href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-foffload-options"
+ ><code>-foffload-options=</code></a> flag and the pre-existing but now
+ documented <a
+ href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-foffload"
+ ><code>-foffload=</code></a> flag.
+ </li>
</ul>
<!-- <h3 id="ada">Ada</h3> -->
@@ -104,6 +112,8 @@ a work-in-progress.</p>
<h3 id="amdgcn">AMD Radeon (GCN)</h3>
<ul>
<li>Debug experience with ROCGDB has been improved.</li>
+ <li>Support for the type <code>__int128_t</code>/<code>integer(kind=16)</code>
+ was added.</li>
</ul>
<!-- <h3 id="arc">ARC</h3> -->
next reply other threads:[~2021-06-29 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 15:34 Tobias Burnus [this message]
2021-06-29 16:38 ` Julian Brown
2021-07-01 17:38 ` Tobias Burnus
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=bc65b173-eaa4-5c49-d5bd-ba82013c86ea@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=andrew_stubbs@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=julian@codesourcery.com \
/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).