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.

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

add atomic to rvfi_instr_if, expand/divide the support pkg #2093

Conversation

silabs-krdosvik
Copy link

Added is_amo and is_atomic instr to rvfi_instr_if. Also restructured the isa_support. Will continue working on isa_support files when the merges from cv32e40s/dev to cv32e40x/dev, and cv32e40s to cv32e40x-dv is done.

Must wait to merge this PR untill openhwgroup/cv32e40x-dv#13 is merged, and we can update the clonetb hash.

Same status as openhwgroup/cv32e40x-dv#13 (ci check passes partially and formal compiles)

lib/support/isa_constants.sv Show resolved Hide resolved
`include "isa_tdefs.sv"
`include "isa_tdefs_csr.sv"
`include "isa_support.sv" //TODO: krdosvik, change name to isa_disassembler when no outstanding PR
`include "isa_functions.sv"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The includes in isa_functions.sv are also already included above this line.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean isa_function is indirectly included by including the isa_support.sv? If that is what you mean: I didnt think about that, is that a problem? If not I think it is more readable to explicitly define what is meant to be included in the package, even though files might already include them.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regardless of the above, all these files needs compile-guards, otherwise there will be issues down the line.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beware of dangers like this:
If 1) an include file has guards, and 2) compilation of all source files is done as one "compilation unit", and 3) two other files include that include file, then C) only one of those other files will get any actual content from the include file.

@silabs-robin
Copy link
Contributor

I think this PR is a stale duplicate of another PR that got merged?
Therefore I'm closing it.

If I'm wrong then please just re-open it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants