Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add extension requirements/implications #118

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add extension requirements/implications #118

wants to merge 1 commit into from
+24 −3

Commits on Sep 17, 2023

  1. Add extension requirements/implications 

    Those implications are useful to capture simpler "an extension specifies
a feature" principle.  For instance, if the 'Za64rs' extension is
implemented (at most 64-byte reservation set), the feature specified by the
'Za128rs' extension is also implemented (at most 128-byte reservation set).
Implying 'Za64rs' → 'Za128rs' makes feature detection logic simpler.

Despite that requiring the 'H' extension to some Sh* extensions in the
specification seems redundant, it will be useful if those extensions are
used separately from the RISC-V Profiles.

Note that one of them ('Smstateen' → 'Ssstateen') is implemented in
GNU Binutils version 2.40 or later.

Signed-off-by: Tsukasa OI <[email protected]>
    @a4lg
    a4lg committed Sep 17, 2023
    Configuration menu
    Copy the full SHA
    0b4aedb View commit details
    Browse the repository at this point in the history