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. 8507122b38e6b60e8f2f3c8cd339d4f318377203 Date: Fri, 7 Jun 2024 07:59:44 +0000 (GMT) [thread overview] Message-ID: <20240607075944.85E32392DFC5@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 8507122b38e6b60e8f2f3c8cd339d4f318377203 (commit) from 1db5b34eb8cf47f070f643f993d835149bce2ec7 (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 8507122b38e6b60e8f2f3c8cd339d4f318377203 Author: Tobias Burnus <tburnus@baylibre.com> Date: Fri Jun 7 09:58:52 2024 +0200 gcc-15/changes.html (nvptx): Constructors are now supported diff --git a/htdocs/gcc-15/changes.html b/htdocs/gcc-15/changes.html index b59fd3be..0ea7bdec 100644 --- a/htdocs/gcc-15/changes.html +++ b/htdocs/gcc-15/changes.html @@ -85,7 +85,14 @@ a work-in-progress.</p> <!-- <h3 id="nios2">Nios II</h3> --> -<!-- <h3 id="nvptx">NVPTX</h3> --> +<h3 id="nvptx">NVPTX</h3> + +<ul> + <li>GCC's nvptx target now supports constructors and destructors. + For this, a recent version of <a + href="https://gcc.gnu.org/install/specific.html#nvptx-x-none" + >nvptx-tools is required</a>.</li> +</ul> <!-- <h3 id="hppa">PA-RISC</h3> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-15/changes.html | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-06-07 7:59 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=20240607075944.85E32392DFC5@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: linkBe 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).