public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Kito Cheng <kito@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 1595be247c3cbe1a24576bf067aa70f61b6d33cb
Date: Thu, 20 Apr 2023 10:20:51 +0000 (GMT)	[thread overview]
Message-ID: <20230420102051.48EC83858C83@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  1595be247c3cbe1a24576bf067aa70f61b6d33cb (commit)
      from  907f21ff6915dda0b466c2236e8202602f72db18 (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 1595be247c3cbe1a24576bf067aa70f61b6d33cb
Author: Kito Cheng <kito.cheng@sifive.com>
Date:   Wed Apr 19 21:50:49 2023 +0800

    gcc-13: Add release note for RISC-V

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index f6941534..4515a6af 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -636,7 +636,34 @@ a work-in-progress.</p>
 
 <h3 id="riscv">RISC-V</h3>
 <ul>
-    <li>New ISA extension support for zawrs.</li>
+    <li>Support for vector intrinsics as specified in <a
+	href="https://github.com/riscv-non-isa/rvv-intrinsic-doc/tree/v0.11.x">
+	version 0.11 of the RISC-V vector intrinsic specification</a>,
+	thanks Ju-Zhe Zhong from <a href="https://rivai-ic.com.cn/">RiVAI</a>
+	for contributing most of implementation.
+    </li>
+    <li>Support for the following standard extensions has been added:
+      <ul>
+        <li>Zawrs</li>
+        <li>Zbkb</li>
+        <li>Zbkc</li>
+        <li>Zbkx</li>
+        <li>Zdinx</li>
+        <li>Zfinx</li>
+        <li>Zfh</li>
+        <li>Zfhmin</li>
+        <li>Zhinx</li>
+        <li>Zhinxmin</li>
+        <li>Zicbom</li>
+        <li>Zicbop</li>
+        <li>Zicboz</li>
+        <li>Zknd</li>
+        <li>Zkne</li>
+        <li>Zksed</li>
+        <li>Zksh</li>
+        <li>Zmmul</li>
+      </ul>
+    </li>
     <li>Support for the following vendor extensions has been added:
       <ul>
         <li>XTheadBa</li>
@@ -659,6 +686,11 @@ a work-in-progress.</p>
         <li>T-Head's XuanTie C906 (<code>thead-c906</code>).</li>
       </ul>
     </li>
+    <li>Improves the multi-lib selection mechanism for the bare-metal toolchain
+	(riscv*-elf*). GCC will now automatically select the best-fit multi-lib
+	candidate instead of requiring all possible reuse rules to be listed at
+	build time.
+    </li>
 </ul>
 
 <!-- <h3 id="rx">RX</h3> -->

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

Summary of changes:
 htdocs/gcc-13/changes.html | 34 +++++++++++++++++++++++++++++++++-
 1 file changed, 33 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-04-20 10: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=20230420102051.48EC83858C83@sourceware.org \
    --to=kito@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).