Submissions of extensions to the Unpriv and Priv ICs for official Architecture Review and for Opcode/CSR Assignment Review (and official allocation) should be emailed to firstname.lastname@example.org. A row for your submission must also be added to the bottom of the Arch Review Status table below, and please fill in all fields except for the Status/ETA field.
Once arch review results have been provided back to the TG, spec changes corresponding to requested changes/corrections/etc. do not need to be re-reviewed. But any other substantive post-review architectural changes must be presented back to the Arch Review committee (using the above email) for approval. Ideally there should not be any such changes, but a simple email summarizing the what and why of any changes is sufficient.
|Extension Name||Included Extensions|
(e.g. Zkr, Zbk[bcx], ...)
|Submitting TG||Contact(s) name and email|
(Chair, Vice-chair, Architect, Editor, etc.)
|Status||Status Date||projected completion date||Comments/blockers/next steps|
Martin Maas (email@example.com)
|Submitted||23 July 2021||Q4 '21||Initial full review completed. Review of eventual updated spec to be done once submitted.|
|Packed SIMD||Zpsfoperand, Zprvsfextra, Zpn, Zbp[??]||P||Chuanhua Chang (firstname.lastname@example.org)||Submitted||24 June 2021||Started, tbd finish|
|psABI||psABI||Software||Kito Cheng (email@example.com)||Submitted||13 April 2022||Q2 '22||Full review|
|Wait on Reservation Set||Zawrs||Fast-track||Vedvyas Shanbhogue (firstname.lastname@example.org)||Submitted||4 May 2022||Q2 '22||Full review|
In addition to the extension spec, please submit information about the PoCs and about utility/efficiency (although we don't need all the gory detail - a paragraph or so for each can be fine). For items considered to not be consequential, a sentence or so explaining why should suffice.
If, for now, you primarily want to nail down opcode/CSR assignment and have a solid draft spec (but not a final spec ready for official Arch Review), then mention this in your email submission so we know to focus on just the opcode/CSR assignments (but in the context of the spec).
Similarly, while a spec is being developed, if there is need for a first-order spec review of certain key architectural assumptions being made (e.g. to make sure that these will ultimately be considered acceptable and appropriate), then explain this in the submission and highlight the key assumptions that we should focus on evaluating for now.
Lastly, note that Arch Review doesn't concern itself with Definition-of-done (DoD) checklist items like Spike/QEMU/Sail support, ACTs, and software support. Waivers are a matter for Tech Chairs to approve, and review of the other DoD requirements occurs through the various IC/HC sign-offs and the overall review/approval by tech-chairs.
The email addresses for the primary reviewers are:
Krste Asanovic <email@example.com>
Andrew Waterman <firstname.lastname@example.org>
John Hauser <email@example.com>
Greg Favor <firstname.lastname@example.org>
Zba, Zbb, Zbc, Zbs (BitManip)
Zfinx, Zdinx, Zhinx, Zhinxmin
Zbkb, Zbkc, Zbkx, Zknd, Zkne, Zknh, Zksed, Zksh, Zkr, Zkn, Zks (Scalar Crypto)
V (and several Zve* extensions)
Zicbom, Zicbop, Zicboz
Svnapot, Svpbmt, Svinval