From: Tobias Burnus <tobias@codesourcery.com>
To: Tom de Vries <tdevries@suse.de>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [Patch][wwwdocs + gcc] nvptx – update for -mptx change – gcc-12/changes.html + gcc/docs/invoke.texi
Date: Wed, 2 Feb 2022 09:30:44 +0100 [thread overview]
Message-ID: <f069981d-5a0c-11d5-db2d-ea4574037eb0@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
This patch updates the documentation for Tom's change of the default
-mptx= version - mentioning also -mptx=7.0.
I forgot whether ptx = 7.0 was working fine or whether there was
a reason not to mention it.
At some point, we also have to update -misa=... Currently, only
sm_30 and sm_35 are documented but sm_53, sm_75 and sm_80 are supported.
Can they now be documented are are there still issues?
OK to commit the wwwdocs + gcc invoke.texi patches?
Tobias
PS: I wonder whether any of the recent changes by chance did fix
https://gcc.gnu.org/PR102429 – nvptx: ICE with expand_GOMP_SIMT_XCHG_BFLY
: in expand_insn, at optabs.c:7947 for DCmode (complex double)
Probably not, but it would have been nice nonetheless.
-----------------
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: invoke.diff --]
[-- Type: text/x-patch, Size: 799 bytes --]
invoke.texi: nvptx – update for -mptx change
gcc/ChangeLog:
* doc/invoke.texi (-mptx): Document new default, add 7.0.
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 7af5c51cc3c..61d7b4f077a 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -27250,9 +27250,9 @@ strings must be lower-case. Valid ISA strings include @samp{sm_30} and
@item -mptx=@var{version-string}
@opindex mptx
-Generate code for given the specified PTX version (e.g.@: @samp{6.3}).
-Valid version strings include @samp{3.1} and @samp{6.3}. The default PTX
-version is 3.1.
+Generate code for given the specified PTX version (e.g.@: @samp{7.0}).
+Valid version strings include @samp{3.1}, @samp{6.3}, and @samp{7.0}.
+The default PTX version is 6.3.
@item -mmainkernel
@opindex mmainkernel
[-- Attachment #3: wwwdocs.diff --]
[-- Type: text/x-patch, Size: 741 bytes --]
gcc-12/changes.html: nvptx – update for -mptx change
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 2719b9d5..bd0babfb 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -404,7 +404,8 @@ a work-in-progress.</p>
<ul>
<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.3</code> (new default) and
+ <code>7.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-02-02 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 8:30 Tobias Burnus [this message]
2022-02-04 11:46 ` Tom de Vries
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=f069981d-5a0c-11d5-db2d-ea4574037eb0@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).