From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Tom de Vries <tdevries@suse.de>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
Thomas Schwinge <thomas@codesourcery.com>
Subject: [wwwdocs][patch] gcc-13/changes.html: Add nvptx's --with-arch
Date: Wed, 28 Sep 2022 09:39:44 +0200 [thread overview]
Message-ID: <f071b915-d4ce-a7c2-beb1-3b8c634d8985@codesourcery.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 379 bytes --]
The attached patch documents the new nvptx configure flag --with-arch=sm_...
Comments? 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: nvptx-with-arch.diff --]
[-- Type: text/x-patch, Size: 956 bytes --]
gcc-13/changes.html: Add nvptx's --with-arch
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 390193ca..f113e443 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -209,7 +209,18 @@ a work-in-progress.</p>
<!-- <h3 id="nios2">Nios II</h3> -->
-<!-- <h3 id="nvptx">NVPTX</h3> -->
+<h3 id="nvptx">NVPTX</h3>
+<ul>
+ <li>The default value for the <a
+ href="https://gcc.gnu.org/onlinedocs/gcc/Nvidia-PTX-Options.html"><code>
+ -march</code></a> option can be now changed when <a
+ href="https://gcc.gnu.org/install/">building GCC</a> using the
+ <a href="https://gcc.gnu.org/install/specific.html#nvptx-x-none">
+ <code>--with-arch=</code></a> flag; if not specified, GCC defaults to
+ <code>sm_30</code>. GCC's target libraries are build both with
+ <code>sm_30</code> and the specified target architecture.
+ </li>
+</ul>
<!-- <h3 id="hppa">PA-RISC</h3> -->
next reply other threads:[~2022-09-28 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 7:39 Tobias Burnus [this message]
2022-09-28 11:03 ` Gerald Pfeifer
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=f071b915-d4ce-a7c2-beb1-3b8c634d8985@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=tdevries@suse.de \
--cc=thomas@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).