Add adoc anchors required by RV32I normative rules #2153
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uals that CTP (Certification Test Plans) will use to have tests link back to the standards. See ISA manual issue 1397 for a lengthy discussion on the topic.
…32I (Chapter 2. RV32I Base Integer Instruction Set)
…e in a later commit. Also changed Makefile to build tags when building other artifacts (i.e., html, PDF, EPUB) because I'll be adding a Ruby gem to check the tags against expected tags (in the future) and to change names to clarify that the tags backend is being using to extract normative rule tags. The same backend with a different prefix could extract other tags if needed someday (so I'm future proofing). Also need to use latest version of docs-resources submodule to get the tags converter backend. This commit requires changes to the tags.rb script in the docs-resources I just made to work. See issue riscv/docs-resources#54
Contributor
Author
|
Forgot to mention that you'll need a version of the docs_resources with my associated PR in it. See riscv/docs-resources#54. |
Contributor
Author
|
Hold on. This supposed to be a PR to my fork not the upstream. I'll kill this. |
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using this as a pilot case to share with stakeholders (e.g., ARC, Doc SIG) what it will look like to start tagging the ISA manual with normative rule text used to create normative rules in the CSC test plans. Will also be useful for processor implementations to understand RISC-V better even if they don't plan on getting a certificate for their implementation.