public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 7644f773bf67640a1240841127b571df3291f312
Date: Tue, 31 Aug 2021 14:24:19 +0000 (GMT)	[thread overview]
Message-ID: <20210831142419.789623858400@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  7644f773bf67640a1240841127b571df3291f312 (commit)
      from  c425fb4443dc598ea3cd1c9209b217b16ddb9146 (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 7644f773bf67640a1240841127b571df3291f312
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Tue Aug 31 16:24:12 2021 +0200

    gcc-12/changes.html: nvptx - new __PTX_SM__ macro

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index a8859882..06d5ea73 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -149,6 +149,8 @@ a work-in-progress.</p>
       for the generated code; permitted values are <code>3.1</code>
       (default, matches previous GCC versions) and <code>6.3</code>.
   </li>
+  <li>The new <code>__PTX_SM__</code> predefined macro allows code to check the
+      compute model being targeted by the compiler.</li>
 </ul>
 <!-- <h3 id="hppa">PA-RISC</h3> -->
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-08-31 14:24 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=20210831142419.789623858400@sourceware.org \
    --to=burnus@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).