Print not specified for floorplan constraints file when running vpr w… #1773
Conversation
This file contains 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
…ithout floorplan constraints
vaughnbetz
reviewed
Jun 21, 2021
|
@sfkhalid : this PR needs to be fixed (bad memory access). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…ithout floorplan constraints
When a floorplan constraints file is not provided when running vpr (i.e. read_vpr_constraints option not used), the VTR log file used print:
Vpr floorplanning constraints file:
Now, it prints the following
Vpr floorplanning constraints file: not specified
This change makes it clear to the user that no constraints file was passed in when running vpr. This fix is for issue #1752