Request for new GH release now Zfa is marked as ratified #1137
Comments
asb
added a commit
to asb/llvm-project
that referenced
this issue
Oct 2, 2023
The Zfa specification was recently ratified <https://wiki.riscv.org/display/HOME/Recently+Ratified+Extensions>. This commit bumps the version to 1.0, but leaves it as an experimental extension (to be done in a follow-on patch), so reviews can focus on confirming there haven't been spec changes we have missed (which as noted below, is more difficult than usual). Because the development of the Zfa spec overlapped with the transition of riscv-isa-manual from LaTeX to AsciiDoc, it's more difficult than usual to confirm version changes. The linked PDF in RISCVUsage is for some reason a 404. Key commit histories to review are: * Changes to zfa.adoc on the main branch <https://github.com/riscv/riscv-isa-manual/commits/main/src/zfa.adoc> * Changes to zfa.tex on the now defunct latex branch <https://github.com/riscv/riscv-isa-manual/commits/latex/src/zfa.tex> From reviewing these, I believe there have been no changes to the spec since version 0.1/0.2 (sadly the AsciiDoc and LaTeX versions of the spec are inconsistent about version numbering). There hasn't been a GitHub release of the spec since Zfa was ratified (though I've requested one <riscv/riscv-isa-manual#1137>), so RISCVUsage is updated to link to the current Zfa.adoc. I don't think we need to block on this, as we expect to shortly move Zfa to non-experimental, at which point we don't link to individual spec documents in RISCVUsage.
|
I've generated a new release, does this meet your needs? https://github.com/riscv/riscv-isa-manual/releases/tag/riscv-isa-release-056b6ff-2023-10-02 |
|
Perfect, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be helpful if we could have a new GH release of the draft spec with generated PDFs now zfa is marked as ratified. This is handy to reference in the corresponding toolchain patches.
The text was updated successfully, but these errors were encountered: