From: Ved Shanbhogue <ved@rivosinc.com>
To: Rob Bradford <rbradford@rivosinc.com>
Cc: Andrew Jones <ajones@ventanamicro.com>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
atishp@rivosinc.com, palmer@dabbelt.com,
alistair.francis@wdc.com, bin.meng@windriver.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com
Subject: Re: Re: Re: [PATCH 1/3] target/riscv: Add infrastructure for 'B' MISA extension
Date: Fri, 12 Jan 2024 18:28:45 -0600 [thread overview]
Message-ID: <ZaHZPZauuZh4SwVj@ved-XPS-8940> (raw)
In-Reply-To: <7461190fbece351f916eccd258bf62b86227927d.camel@rivosinc.com>
Rob Bradford wrote:
>I'm using table 27.1 in the published PDF which is the PDF in this
>release:
>https://github.com/riscv/riscv-isa-manual/releases/tag/Ratified-IMAFDQC
>It looks like it was removed in this commit (which is a set of
>backports):
>
We would retain the previously documented canonical order with B
between C and P and that table updated on ratification.
regards
ved
next prev parent reply other threads:[~2024-01-13 1:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 17:07 [PATCH 0/3] target/riscv: Add support for 'B' extension Rob Bradford
2024-01-09 17:07 ` [PATCH 1/3] target/riscv: Add infrastructure for 'B' MISA extension Rob Bradford
2024-01-10 18:18 ` Daniel Henrique Barboza
2024-01-11 13:07 ` Andrew Jones
2024-01-11 13:14 ` Andrew Jones
2024-01-11 15:17 ` Rob Bradford
2024-01-12 16:08 ` Andrew Jones
2024-01-12 16:54 ` Rob Bradford
2024-01-13 0:28 ` Ved Shanbhogue [this message]
2024-01-11 13:15 ` Andrew Jones
2024-01-09 17:07 ` [PATCH 2/3] target/riscv: Add step to validate 'B' extension Rob Bradford
2024-01-10 18:26 ` Daniel Henrique Barboza
2024-01-11 13:09 ` Andrew Jones
2024-01-09 17:07 ` [PATCH 3/3] target/riscv: Enable 'B' extension on max CPU type Rob Bradford
2024-01-10 18:32 ` Daniel Henrique Barboza
2024-01-10 18:41 ` Daniel Henrique Barboza
2024-01-11 13:02 ` Andrew Jones
2024-01-11 14:53 ` Daniel Henrique Barboza
2024-01-11 15:49 ` Rob Bradford
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=ZaHZPZauuZh4SwVj@ved-XPS-8940 \
--to=ved@rivosinc.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=atishp@rivosinc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=rbradford@rivosinc.com \
--cc=zhiwei_liu@linux.alibaba.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 NNTP newsgroup(s).