-
Notifications
You must be signed in to change notification settings - Fork 173
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.
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
Move extension scattered enum to single file #634
Conversation
This doesn’t work for sail-cheri-riscv. |
I think the enumeration should probably remain scattered, but it seems to me there are two cases:
|
Hmm good point about CHERI. Unfortunately it isn't just misa. There's also things like menvcfg/mseccfg which have circular dependencies. I guess technically the right thing to do would be to make How about we keep it scattered but still move them all into one file? |
True, but IMO sail-cheri-riscv should change to just be a diff on top of the base model. That would make upstreaming a lot easier as well. |
It should, but it won’t do so immediately, and the model has been designed to support the current approach, so we do need to uphold that. |
21a44d6
to
25c5b01
Compare
25c5b01
to
859a49c
Compare
859a49c
to
8a70125
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now that comments are consistently added. Keeping it as a scattered enum should avoid the issues with CHERI while giving us the benefit of simpler file ordering.
I wonder if it might be nicer to order the extensions by canonical order instead of alphabetically so that extensions like Zfinx and Zdinx are next to each other, but it's also fine as it is. If you wanted to use the same ordering that I put in the README that would work.
Having this distributed through the code can lead to slightly awkward dependency order issues. We need to keep it scattered though so e.g. CHERI can add its extensions.
8a70125
to
0f89f4e
Compare
Sorted according to the canonical ordering. Which actually doesn't make any sense for |
Hmm. Really should've been named |
Having this distributed through the code can lead to slightly awkward dependency order issues. We need to keep it scattered though so e.g. CHERI can add its extensions.
Fixes #633