From: Gerald Pfeifer <gerald@pfeifer.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: gcc-patches@gcc.gnu.org, kito.cheng@gmail.com
Subject: Re: [PATCH 3/3] RISC-V: Support version controling for ISA standard extensions
Date: Tue, 15 Dec 2020 09:08:07 +0100 (CET) [thread overview]
Message-ID: <57f217a9-926d-4a58-2a3f-e7f5a35aa66c@pfeifer.com> (raw)
In-Reply-To: <20201113072910.42353-4-kito.cheng@sifive.com>
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
next prev parent reply other threads:[~2020-12-15 8:08 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 [this message]
2020-12-17 3:44 ` Kito Cheng
[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=57f217a9-926d-4a58-2a3f-e7f5a35aa66c@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.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).