Krste Asanovic

To be revisited after spec goes out, but yes plan is to extend naming in backwards-compatible way by requiring non-p letter after numeric digits.

Providing a trap fence should probably be more global than just vector instructions, though it might have variants that allowed selection of a subset of traps.

Labeling as post v1.0, though is really a broader issue than vector extension.

General rule is that extension names imply the things they require, and we take union of all implied features. This simplifies model when string is built up in pieces in...

Agree it is useful. This is being looked at.

There should be a later vector extension with greater support for fixed-point operations, and don't want to add more to vector spec before 1.0.

Adding a new alternative for agnostic carries a documentation/verification/compatibility cost. Forcing a 1 is very cheap. In case 1, generating the result will cost more than filling with constant value...

I was indeed perhaps too hasty in closing this issue, so reopening for comment.

I believe there is a value in allowing masks to always write their whole result register ignoring vector length value, vl, as they are always tail-agnostic and this would eliminate...

Computed mask results added as option in https://github.com/riscv/riscv-v-spec/commit/fd4565e18d882d3ad2df8592be81034bafac1b71 If there's sufficient interest in expanding the set for data, this could be explored as compatible option post v1.0, so labeling this...