added bounds check for forced primitive site #2671
Merged
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
github-actions
bot
added
VPR
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.
When seeking a primitive site matching a user-specified site index, verify that the index is within the available range for the primitive type within the current physical block type.
Description
Added a bounds check and error message.
Related Issue
Motivation and Context
A error message that alerts the user to out of bounds indices helps to identify indexing errors in externally generated flat placements. For example, ISPD placement tools use different indexing for LUTs than is required by the legalizer.
How Has This Been Tested?
Tested by legalizing ISPD placements with and without out of bounds site indices.
Types of changes
Checklist: