1. Tech-Vector-Ext
  2. Messages

Re: RISC-V Vector Extension post-public review updates

Greg Favor
 

On Mon, Nov 15, 2021 at 1:05 PM Krste Asanovic <krste@...> wrote:
1) Mandate all implementations raise an illegal exception in this
case.  This is my preferred route, as this would be a minor errata for
existing implementations (doesn't affect software), and we would not reuse
this state/encoding for other purposes.

2) Allow either correct execution or illegal exception (as with
misaligned). 

3) Consider "reserved", implying implementations that support it are
non-conforming unless we later go with 2).

I'm assuming we're going to push to ratify 1) unless I hear strong objections.

 If I understand correctly, #3 is like #1 near-term (for conforming implementations), but keeps the possibility open to later changing from "always illegal exception" to something else.

I'd vote for #1 or #3, and would be perfectly fine with #1.

Greg
Join {tech-vector-ext@lists.riscv.org to automatically receive all group messages.