From: Michael Clark <mjc@sifive.com>
To: qemu-devel@nongnu.org
Cc: patches@groups.riscv.org, Michael Clark <mjc@sifive.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmer@sifive.com>
Subject: [Qemu-devel] [PATCH v4 12/26] RISC-V: Update E order and I extension order
Date: Mon, 19 Mar 2018 14:18:35 -0700 [thread overview]
Message-ID: <1521494329-19546-13-git-send-email-mjc@sifive.com> (raw)
In-Reply-To: <1521494329-19546-1-git-send-email-mjc@sifive.com>
Section 22.8 Subset Naming Convention of the RISC-V ISA Specification
defines the canonical order for extensions in the ISA string. It is
silent on the position of the E extension however E is a substitute
for I so it must come early in the extension list order. A comment
is added to state E and I are mutually exclusive, as the E extension
will be added to the RISC-V port in the future.
Cc: Sagar Karandikar <sagark@eecs.berkeley.edu>
Cc: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Signed-off-by: Michael Clark <mjc@sifive.com>
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
---
target/riscv/cpu.c | 2 +-
target/riscv/cpu.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
index 4851890..d2ae56a 100644
--- a/target/riscv/cpu.c
+++ b/target/riscv/cpu.c
@@ -26,7 +26,7 @@
/* RISC-V CPU definitions */
-static const char riscv_exts[26] = "IMAFDQECLBJTPVNSUHKORWXYZG";
+static const char riscv_exts[26] = "IEMAFDQCLBJTPVNSUHKORWXYZG";
const char * const riscv_int_regnames[] = {
"zero", "ra ", "sp ", "gp ", "tp ", "t0 ", "t1 ", "t2 ",
diff --git a/target/riscv/cpu.h b/target/riscv/cpu.h
index cff02a2..3a0ca2f 100644
--- a/target/riscv/cpu.h
+++ b/target/riscv/cpu.h
@@ -71,6 +71,7 @@
#define RV(x) ((target_ulong)1 << (x - 'A'))
#define RVI RV('I')
+#define RVE RV('E') /* E and I are mutually exclusive */
#define RVM RV('M')
#define RVA RV('A')
#define RVF RV('F')
--
2.7.0
next prev parent reply other threads:[~2018-03-19 21:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 21:18 [Qemu-devel] [PATCH v4 00/26] RISC-V Post-merge spec conformance and cleanup Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 01/26] RISC-V: Make virt create_fdt interface consistent Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 02/26] RISC-V: Replace hardcoded constants with enum values Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 03/26] RISC-V: Make virt board description match spike Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 04/26] RISC-V: Use ROM base address and size from memmap Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 05/26] RISC-V: Remove identity_translate from load_elf Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 06/26] RISC-V: Mark ROM read-only after copying in code Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 07/26] RISC-V: Remove unused class definitions Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 08/26] RISC-V: Make sure rom has space for fdt Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 09/26] RISC-V: Include intruction hex in disassembly Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 10/26] RISC-V: Hold rcu_read_lock when accessing memory Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 11/26] RISC-V: Improve page table walker spec compliance Michael Clark
2018-03-19 21:18 ` Michael Clark [this message]
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 13/26] RISC-V: Make some header guards more specific Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 14/26] RISC-V: Make virt header comment title consistent Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 15/26] RISC-V: Use memory_region_is_ram in pte update Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 16/26] RISC-V: Remove EM_RISCV ELF_MACHINE indirection Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 17/26] RISC-V: Hardwire satp to 0 for no-mmu case Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 18/26] RISC-V: Remove braces from satp case statement Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 19/26] RISC-V: riscv-qemu port supports sv39 and sv48 Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 20/26] RISC-V: vectored traps are optional Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 21/26] RISC-V: No traps on writes to misa, minstret, mcycle Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 22/26] RISC-V: Remove support for adhoc X_COP interrupt Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 23/26] RISC-V: Convert cpu definition towards future model Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 24/26] RISC-V: Clear mtval/stval on exceptions without info Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 25/26] RISC-V: Remove erroneous comment from translate.c Michael Clark
2018-03-19 21:18 ` [Qemu-devel] [PATCH v4 26/26] RISC-V: Fix riscv_isa_string memory size bug Michael Clark
2018-03-20 11:51 ` Peter Maydell
2018-03-20 20:51 ` Philippe Mathieu-Daudé
2018-03-20 21:35 ` [Qemu-devel] [patches] " Michael Clark
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=1521494329-19546-13-git-send-email-mjc@sifive.com \
--to=mjc@sifive.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--cc=qemu-devel@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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 NNTP newsgroup(s).