Disambiguate the use of the term "reserved" for HINT instructions #990
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.
As was raised in #300, the overloaded use of the term "reserved" when listing HINT encodings is potentially confusing. As clarified in that thread, these encodings are "reserved" in the intuitive English language meaning of the word, but are not part of the "reserved instruction-set category" as defined in the section 1.3 introduction and further elaborated in section 2.2 "Base Instruction Formats" (which notes how platforms can choose to raise an illegal-instruction exception for reserved instruction encodings).