Revise Multichip routing #2430
Merged
Revise Multichip routing #2430
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
No one constructs the objects, so only the accessor methods need be compatible.
…evice These were being erroneously routed off-chip!
This also makes the error device optional
Previously the algorithm: 1- explore islands of nodes connected by :*=* 2- if there are both :*= and :=* connected to the island, report error 3- if there is a :*= connected to the island, change all :*=* to :*= 4- if there is a :=* connected to the island, change all :*=* to :=* 5- default to :=* The new algorithm: 1- categorize nodes into arityDirectionFlexible or not (only Adapters are flexible for now) 2- when asked to resolve a :*=* start exploration on the flexible side (if any, else :=) 3- explore islands of flexible nodes connected by :*=* 4- if there are both :*= and :=* connected to the island, report error 5- if there is a :*= connected to the island, change all :*=* to :*= 6- if there is a :=* connected to the island, change all :*=* to :=* 7- default to :=
terpstra
force-pushed
the
revised-multichip-routing
branch
from
69b89ca
to
3ee1461
Compare
hcook
approved these changes
Apr 26, 2020
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.
JunctionNodes now support configurable up/down connection ratio.
RegionReplicator and AddressAdjuster now takes a region+local AddressSet instead of a mask (MultiChipMaskKey was removed).
AddressAdjuster can now optionally leave off the 'remote' side of the connection.
Type of change: other enhancement
Impact: API modification
Development Phase: implementation
Release Notes
AddressAdjuster and RegionReplicator now work on prefixes (not chip id)