Automated OpenROAD setup for a given verilog file#1
Open
dobios wants to merge 7 commits into
Open
Conversation
dobios
changed the title
TaoBi22
force-pushed
the
dobios/openroad-integration
branch
from
8ba2eac to
ef8425f
Compare
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
1 participant
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.
I made a first attempt at automating the process of: "given a verilog file, setup all of the stuff you need to run the openroad flow". I am a total noob at Makefile, so I won't attempt to butcher your very clean file to add this into the loop, maybe we should sync up and do that together @TaoBi22