public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 7628017f4f79e9ba4f449cc6e24bc1f36c0adf84
Date: Tue,  5 Apr 2022 08:20:11 +0000 (GMT)	[thread overview]
Message-ID: <20220405082011.B42613858D37@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  7628017f4f79e9ba4f449cc6e24bc1f36c0adf84 (commit)
      from  8ea26ed30b580df09f63ed90c1a14f27b7bb97c0 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7628017f4f79e9ba4f449cc6e24bc1f36c0adf84
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Mar 30 14:14:06 2022 +0200

    gcc-12: Nvptx updates.
    
    Co-Authored-By: Tobias Burnus <tobias@codesourcery.com>

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4e1f6b0f..4f2ee77f 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -561,12 +561,33 @@ a work-in-progress.</p>
 
 <h3 id="nvptx">NVPTX</h3>
 <ul>
+  <li>The <code>-march</code> flag has been added.  The <code>-misa</code>
+    flag is now considered an alias of the <code>-march</code> flag.</li>
+  <li>Support for PTX ISA target architectures <code>sm_53</code>,
+    <code>sm_70</code>, <code>sm_75</code> and <code>sm_80</code> has been
+    added.  These can be specified using the <code>-march</code> flag.</li>
+  <li>The default PTX ISA target architecture has been set back
+    to <code>sm_30</code>, to fix support for <code>sm_30</code> boards.</li>
+  <li>The <code>-march-map</code> flag has been added.  The
+    <code>-march-map</code> value will be mapped to an valid
+    <code>-march</code> flag value.  For instance,
+    <code>-march-map=sm_50</code> maps to <code>-march=sm_35</code>.
+    This can be used to specify that generated code is to be executed on a
+    board with at least some specific compute capability, without having to
+    know the valid values for the <code>-march</code> flag.</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>-march</code> but at least <code>6.0</code>.
   </li>
+  <li>An <code>mptx-3.1</code> multilib was added.  This allows using older
+      drivers which do not support PTX ISA version 6.0.</li>
   <li>The new <code>__PTX_SM__</code> predefined macro allows code to check the
-      compute model being targeted by the compiler.</li>
+      PTX ISA target architecture being targeted by the compiler.</li>
+  <li>The new <code>__PTX_ISA_VERSION_MAJOR__</code>
+      and <code>__PTX_ISA_VERSION_MINOR__</code> predefined macros allows code
+      to check the PTX ISA version being targeted by the compiler.</li>
 </ul>
 <!-- <h3 id="hppa">PA-RISC</h3> -->
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-12/changes.html | 25 +++++++++++++++++++++++--
 1 file changed, 23 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-04-05  8:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220405082011.B42613858D37@sourceware.org \
    --to=vries@sourceware.org \
    --cc=gcc-cvs-wwwdocs@gcc.gnu.org \
    /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).