-
Notifications
You must be signed in to change notification settings - Fork 15
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
Tag register information with encapsulating extension(s) #15
Comments
Looking into this! |
Hi, I had started working on this but figured I needed some help. Would the change only reflect in how the sail parser parses sail riscv or are we changing the sail riscv model to something like this?
|
The goal is that the Sail parser/backends are ignorant, and all information is accurately and completely represented in Sail (and then in JSON).
Let utilize the
So, the condition above would become Does scoping allow this to work? The Sail language manual has no discussion on scoping, so maybe everything is at global scope?
Same.
Going back to your original question:
Yes. |
Makes sense! The code was more pseudocode less real code, just to get an idea. Working on this! |
Registers are defined in the Sail code in various places. These definitions should only manifest if the encapsulating extension(s) are enabled, and it should be easily determined when parsing in which extension(s), if any, each register is encapsulated.
The text was updated successfully, but these errors were encountered: