Solving critical path in CLIC target#17
Open
yvantor wants to merge 17 commits into
Open
Conversation
Since this is priority logic it might yield slightly less efficient hardware but have to look into that yet.
alex96295
changed the title
Author
|
@ezelioli I will do a rebase next week, will you have time to review this PR? Thanks |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This commit aims at resolving the critical path that originates in the CLIC target. Such critical path was detected in Carfield and Astral. This mod was tested working in Carfield's CI and is linked to #266.