public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: jiawei@iscas.ac.cn
To: kito.cheng@sifive.com
Cc: gcc-patches@gcc.gnu.org
Subject: RE: [wwwdocs] gcc-13: Add release note for RISC-V
Date: Thu, 20 Apr 2023 14:22:40 +0800 (GMT+08:00)	[thread overview]
Message-ID: <26d005b3.1e97c.1879d544e64.Coremail.jiawei@iscas.ac.cn> (raw)

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

> ---
>  htdocs/gcc-13/changes.html | 31 ++++++++++++++++++++++++++++++-
>  1 file changed, 30 insertions(+), 1 deletion(-)
> 
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index f6941534..5427f805 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -636,9 +636,32 @@ a work-in-progress.</p>
>  
>  <h3 id="riscv">RISC-V</h3>
>  <ul>
> -    <li>New ISA extension support for zawrs.</li>
> +    <li>Supports 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 vendor extensions has been added:
>        <ul>
> +	<li>Zawrs</li>
> +	<li>Zicbom</li>
> +	<li>Zicboz</li>
> +	<li>Zicbop</li>
> +	<li>Zfh</li>
> +	<li>Zfhmin</li>
> +	<li>Zmmul</li>
> +	<li>Zdinx</li>
> +	<li>Zfinx</li>
> +	<li>Zhinx</li>
> +	<li>Zhinxmin</li>
> +	<li>Zksh</li>
> +	<li>Zksed</li>
> +	<li>Zknd</li>
> +	<li>Zkne</li>
> +	<li>Zbkb</li>
> +	<li>Zbkc</li>
> +	<li>Zbkx</li>
>          <li>XTheadBa</li>
>          <li>XTheadBb</li>
>          <li>XTheadBs</li>
> @@ -657,8 +680,14 @@ a work-in-progress.</p>
>        option (GCC identifiers in parentheses).
>        <ul>
>          <li>T-Head's XuanTie C906 (<code>thead-c906</code>).</li>
> +        <li>Ventana's VT1 (<code>ventana-vt1</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> -->
> -- 
> 2.39.2LGTM, do we missed the timeline to merge code size reduction extensions support in gcc13?https://gcc.gnu.org/pipermail/gcc-patches/2023-April/615287.html

             reply	other threads:[~2023-04-20  6:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  6:22 jiawei [this message]
2023-04-20  6:35 ` Kito Cheng
  -- strict thread matches above, loose matches on Subject: below --
2023-04-19 13:53 Kito Cheng
2023-04-19 14:38 ` 钟居哲
2023-04-19 14:42 ` Palmer Dabbelt
2023-04-19 15:08   ` Kito Cheng

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=26d005b3.1e97c.1879d544e64.Coremail.jiawei@iscas.ac.cn \
    --to=jiawei@iscas.ac.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kito.cheng@sifive.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).