forked from lowRISC/ibex
-
Notifications
You must be signed in to change notification settings - Fork 34
fix #300 #313
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
Merged
Merged
fix #300 #313
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
This will work in simulation. Will synthesis produce the expected results?
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.
it should yes - but we should try with some real co-processor
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.
I am not worried about the case when there is a module connected to the XIF and the parameter
XInterfaceis set to 1. That will work as expected in both simulation and synthesis. What is less clear is what will be produced in synthesis whenXInterfaceis 0.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.
In that case,
coproc_donewill always be1as its default value is set hereand it could go to zero only if this statement is true.
This can never be as the
XInterfaceparameter would be0at design time - so the synthesizer would simply remove this logic, and there should not be any latch inferred.Similarly, as this if statement would always be
0, thecoproc_donevalue here would never be assigned, so it would keep its default value at 1 - if you prefer for readability, I can doelse coproc_done = 1'b1- that's why whenXInterfaceis0the CPU isSequentially Equivalent.If instead you refer to the situation that there is an
illegal instructionand you are in theMULTI_CYCLEstate, then no worries, you can never be here as you would never been entered this state if illegals and XInterace is0. That's why whenXInterfaceis0the CPU isSequentially Equivalent.