public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <tburnus@baylibre.com>
Cc: Thomas Schwinge <tschwinge@baylibre.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] gcc-15/changes.html (nvptx): Constructors are now supported
Date: Thu, 6 Jun 2024 00:48:25 +0200 (CEST)	[thread overview]
Message-ID: <651edc41-cc5c-29c1-c167-bb574b122e6c@pfeifer.com> (raw)
In-Reply-To: <afbe99dc-ae70-4fdf-bd5a-de4d500f4f69@baylibre.com>

Hi Tobias,

On Mon, 3 Jun 2024, Tobias Burnus wrote:
> Comments or fine as is?

+<h3 id="nvptx">NVPTX</h3>
+
+<ul>
+  <li>GCC's nvptx target now supports constructors and destructors;

I'd make this a full stop/distinct sentence and ...

+      for this, a recent version of nvptx-tools is <a
+      href="https://gcc.gnu.org/install/specific.html#nvptx-x-none"
+      >required</a>.

... make "nvptx-tools is required" the link text.

Okay with these changes.

Thanks,
Gerald

      parent reply	other threads:[~2024-06-05 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  8:09 Tobias Burnus
2024-06-05 18:01 ` *ping* – " Tobias Burnus
2024-06-05 22:48 ` Gerald Pfeifer [this message]

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=651edc41-cc5c-29c1-c167-bb574b122e6c@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tburnus@baylibre.com \
    --cc=tschwinge@baylibre.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).