Public Review for Zimop and Zcmop Standard Extensions

[Ved Shanbhogue]

Greetings!

We are delighted to announce the start of the public review period for
the May-Be-Ops Fast Track Specification and its extensions Zimop and
Zcmop. The 45-day review period begins today, December 22, and ends on
February 5. This extension falls under the Unprivileged Specification.

The specification can be obtained as a PDF here:
https://drive.google.com/file/d/1ZRQzKSPhG9wwGv08bx8XEpzbJ8zzrNcR/view

This document was generated from the source available in the following
GitHub repository:
https://github.com/riscv/riscv-isa-manual/blob/main/src/zimop.adoc

To respond to the public review, please either email comments to the
public RISC-V ISA-Dev mailing list at <isa...@groups.riscv.org> or add
issues to the GitHub repo:
    https://github.com/riscv/riscv-isa-manual/issues

If you encounter any issues accessing the document or the GitHub link,
please don't hesitate to reach out. We're happy to provide assistance
or offer the document in an alternate format upon request.

We welcome all input and appreciate your time and effort in helping us
by reviewing the specification.

During the public review period, corrections, comments, and suggestions
will be collected for review by the Unprivileged ISA Committee.  Any
minor corrections and/or uncontroversial changes will be incorporated
into the specification. Any remaining issues or proposed changes will
be addressed in the public review summary report. If there are no
issues that require incompatible changes to the public review
specification, the Unprivileged ISA Committee will recommend the
updated specifications be approved and ratified by the RISC-V Technical
Steering Committee and the RISC-V Board of Directors.

Thanks to all the contributors for their hard work.

Regards,
Andrew Waterman
Ved Shanbhogue

[Ved Shanbhogue]

Greetings !

The review period for the May-Be-Ops Fast Track Specification
and its extensions, Zimop and Zcmop, ended on February 5.

During the review, Paul Clayton sought clarifications and made
a suggestion to redefine existing, possibly redundant,
instructions as Zimop/Zcmop [1]. These were responded to [2]
with examples of the use cases and reasons to not redefine
existing instructions or encodings designated as HINTs for
this purpose.

We extend our thanks to all who contributed valuable insights
during the review.

regards,
Andrew, Ved

[1] https://groups.google.com/a/groups.riscv.org/g/isa-dev/c/N6dqRIOd80w/m/Uzt1SohSAQAJ
[2] https://groups.google.com/a/groups.riscv.org/g/isa-dev/c/N6dqRIOd80w/m/A07-eb2bAQAJ