public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 3/3] RISC-V: Support version controling for ISA standard extensions
Date: Thu, 17 Dec 2020 11:44:26 +0800	[thread overview]
Message-ID: <CA+yXCZB0BvPRCDOYUcXf26BsjB9ENz3KBiGpR2NOvmTEujTCyg@mail.gmail.com> (raw)
In-Reply-To: <57f217a9-926d-4a58-2a3f-e7f5a35aa66c@pfeifer.com>

Hi Gerald:

Thanks for notifying me, we'll update that page soon :)

On Tue, Dec 15, 2020 at 4:08 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Fri, 13 Nov 2020, Kito Cheng wrote:
> >  - New option -misa-spec support: -misa-spec=[2.2|20190608|20191213] and
> >    corresponding configuration option --with-isa-spec.
>
> I noticed https://gcc.gnu.org/gcc-11/changes.html is currently empty.
>
> Are you planning to add updates for the GCC 11 release?  (It may be
> useful to add them as they happen, so they we won't miss them and
> also for the benefit of users tracking development.)
>
> Gerald

  reply	other threads:[~2020-12-17  3:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  7:29 [PATCH 0/3] " Kito Cheng
2020-11-13  7:29 ` [PATCH 1/3] RISC-V: Handle implied extension in canonical ordering Kito Cheng
2020-11-13  7:29 ` [PATCH 2/3] RISC-V: Support zicsr and zifencei extension for -march Kito Cheng
2020-11-17 21:23   ` Jim Wilson
2020-11-18  5:44     ` Kito Cheng
2020-11-13  7:29 ` [PATCH 3/3] RISC-V: Support version controling for ISA standard extensions Kito Cheng
2020-11-13  7:34   ` Kito Cheng
2020-12-15  8:08   ` Gerald Pfeifer
2020-12-17  3:44     ` Kito Cheng [this message]
     [not found] <Kito Cheng <kito.cheng@sifive.com>
2020-11-13  7:27 ` Kito Cheng
2020-11-13  7:27   ` [PATCH 3/3] " Kito Cheng
2020-11-17 21:29     ` Jim Wilson
2020-11-18  5:44       ` 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=CA+yXCZB0BvPRCDOYUcXf26BsjB9ENz3KBiGpR2NOvmTEujTCyg@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --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).