From: Kito Cheng <kito.cheng@sifive.com>
To: jiawei@iscas.ac.cn
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] gcc-13: Add release note for RISC-V
Date: Thu, 20 Apr 2023 14:35:23 +0800 [thread overview]
Message-ID: <CALLt3TjaPCiwQb-H31SV_Lvmx8S41tLQTHeBityXs8d6=uG6MA@mail.gmail.com> (raw)
In-Reply-To: <26d005b3.1e97c.1879d544e64.Coremail.jiawei@iscas.ac.cn>
> LGTM, do we missed the timeline to merge code size reduction extensions support in gcc13?
Yeah, GCC 13 is branching out, so we need to wait for GCC 14, I also
really want to have this in GCC 13 too, and I am a little concerned
that it is still not officially ratified yet for merge that.
>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-April/615287.html
next prev parent reply other threads:[~2023-04-20 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 6:22 jiawei
2023-04-20 6:35 ` Kito Cheng [this message]
-- 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='CALLt3TjaPCiwQb-H31SV_Lvmx8S41tLQTHeBityXs8d6=uG6MA@mail.gmail.com' \
--to=kito.cheng@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
/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).