From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Add the Zihpm and Zicntr extensions
Date: Sun, 20 Nov 2022 09:19:31 -0700 [thread overview]
Message-ID: <ed4234e2-3263-2ae2-3f7b-04699e7cbc97@gmail.com> (raw)
In-Reply-To: <20221109030036.19175-1-palmer@rivosinc.com>
On 11/8/22 20:00, Palmer Dabbelt wrote:
> These extensions were recently frozen [1]. As per Andrew's post [2]
> we're meant to ignore these in software, this just adds them to the list
> of allowed extensions and otherwise ignores them. I added these under
> SPEC_CLASS_NONE even though the PDF lists them as 20190614 because it
> seems pointless to add another spec class just to accept two extensions
> we then ignore.
>
> 1: https://groups.google.com/a/groups.riscv.org/g/isa-dev/c/HZGoqP1eyps/m/GTNKRLJoAQAJ
> 2: https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/QKjQhChrq9Q/m/7gqdkctgAgAJ
>
> gcc/ChangeLog
>
> * common/config/riscv/riscv-common.cc: Add Zihpm and Zicnttr
> extensions.
So the idea here is just to define the extension so that it gets defined
in the ISA strings and passed through to the assembler, right?
Jeff
next prev parent reply other threads:[~2022-11-20 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 3:00 Palmer Dabbelt
2022-11-18 2:14 ` Christoph Müllner
2022-11-18 4:29 ` Palmer Dabbelt
2022-11-20 16:19 ` Jeff Law [this message]
2022-11-21 1:36 ` Kito Cheng
2022-11-22 15:20 ` Jeff Law
2022-11-22 15:29 ` Palmer Dabbelt
2022-11-22 21:50 ` Jeff Law
2022-11-22 22:00 ` Palmer Dabbelt
2024-01-19 8:01 ` 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=ed4234e2-3263-2ae2-3f7b-04699e7cbc97@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=palmer@rivosinc.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).