From: Tobias Burnus <tobias@codesourcery.com>
To: Tom de Vries <tdevries@suse.de>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs][patch] gcc-12/changes.html: Document -misa update for nvptx
Date: Thu, 3 Mar 2022 13:27:44 +0100 [thread overview]
Message-ID: <1ffa4e66-af1a-4392-795a-31a8f0047c92@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
The current wording, https://gcc.gnu.org/gcc-12/changes.html#nvptx ,
is outdated and (now wrongly) encourages to use -mptx=.
Updated as follows.
OK?
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
[-- Attachment #2: wwwdocs.diff --]
[-- Type: text/x-patch, Size: 1122 bytes --]
gcc-12/changes.html: Document -misa update for nvptx
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index a3e46eeb..63e2bf63 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -468,9 +468,14 @@ a work-in-progress.</p>
<h3 id="nvptx">NVPTX</h3>
<ul>
+ <li>The <code>-misa/<code> flag now supports <code>sm_53</code>,
+ <code>sm_70</code>, <code>sm_75</code>, and <code>sm_80</code> besides
+ <code>sm_30</code> and <code>sm_35</code> (which is the default).</li>
<li>The <code>-mptx</code> flag has been added to specify the PTX ISA version
for the generated code; permitted values are <code>3.1</code>
- (default, matches previous GCC versions) and <code>6.3</code>.
+ (matches previous GCC versions), <code>6.0</code>, <code>6.3</code>,
+ and <code>7.0</code>. If not specified, the used version is the minimal
+ version required for <code>-misa</code> but at least <code>6.0</code>.
</li>
<li>The new <code>__PTX_SM__</code> predefined macro allows code to check the
compute model being targeted by the compiler.</li>
next reply other threads:[~2022-03-03 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 12:27 Tobias Burnus [this message]
2022-03-30 12:27 ` [wwwdocs][patch] gcc-12: Nvptx updates Tom de Vries
2022-04-05 15:14 ` Proposal to remove '--with-cuda-driver' (was: [wwwdocs][patch] gcc-12: Nvptx updates) Thomas Schwinge
2022-04-05 18:46 ` Roger Sayle
2022-04-29 13:55 ` Proposal to remove '--with-cuda-driver' Thomas Schwinge
2022-04-06 9:57 ` Proposal to remove '--with-cuda-driver' (was: [wwwdocs][patch] gcc-12: Nvptx updates) Tom de Vries
2022-04-29 13:48 ` Proposal to remove '--with-cuda-driver' Thomas Schwinge
2022-05-13 12:29 ` libgomp nvptx plugin: Remove '--with-cuda-driver=[...]' etc. configuration option (was: Proposal to remove '--with-cuda-driver') Thomas Schwinge
2022-05-27 11:57 ` [PING] " Thomas Schwinge
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=1ffa4e66-af1a-4392-795a-31a8f0047c92@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tdevries@suse.de \
/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).