public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-8274] RISC-V: Add the Zihpm and Zicntr extensions
Date: Fri, 19 Jan 2024 08:05:19 +0000 (GMT)	[thread overview]
Message-ID: <20240119080519.EBFA93858430@sourceware.org> (raw)

https://gcc.gnu.org/g:730a801f950e7817696067906cf40d590688387a

commit r14-8274-g730a801f950e7817696067906cf40d590688387a
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Tue Nov 8 19:00:36 2022 -0800

    RISC-V: Add the Zihpm and Zicntr extensions
    
    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.

Diff:
---
 gcc/common/config/riscv/riscv-common.cc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/common/config/riscv/riscv-common.cc b/gcc/common/config/riscv/riscv-common.cc
index 958a6925a6d..4da7f37303b 100644
--- a/gcc/common/config/riscv/riscv-common.cc
+++ b/gcc/common/config/riscv/riscv-common.cc
@@ -279,6 +279,9 @@ static const struct riscv_ext_version riscv_ext_version_table[] =
   {"zicbom",ISA_SPEC_CLASS_NONE, 1, 0},
   {"zicbop",ISA_SPEC_CLASS_NONE, 1, 0},
 
+  {"zicntr", ISA_SPEC_CLASS_NONE, 2, 0},
+  {"zihpm",  ISA_SPEC_CLASS_NONE, 2, 0},
+
   {"zk",    ISA_SPEC_CLASS_NONE, 1, 0},
   {"zkn",   ISA_SPEC_CLASS_NONE, 1, 0},
   {"zks",   ISA_SPEC_CLASS_NONE, 1, 0},

                 reply	other threads:[~2024-01-19  8:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240119080519.EBFA93858430@sourceware.org \
    --to=kito@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).