You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For #575 and future updates to work correctly, PIPs will need to properly set PIP.setIsReversed() on bidirectional PIPs. This is most optimally done at the point of creation in the correct context. This issue requests a new helper method that can be used to ensure and/or correct PIPs that do not have this flag set properly with the expense of O(n), where n is the number of PIPs on the net.
The text was updated successfully, but these errors were encountered:
@clavin-xlnx In light of #774, is there still a need for this helper method?
This issue references #575, which is responsible for unrouting nets, stating that it relies on PIP.isReversed() to be correct to function correctly. With #774, RWRoute should now set this flag correctly.
@clavin-xlnx In light of #774, is there still a need for this helper method?
This issue references #575, which is responsible for unrouting nets, stating that it relies on PIP.isReversed() to be correct to function correctly. With #774, RWRoute should now set this flag correctly.
I suppose it becomes less important, I suppose for other users developing routing solutions they can either manage the issue on their own or write their own helper method.
For #575 and future updates to work correctly, PIPs will need to properly set
PIP.setIsReversed()
on bidirectional PIPs. This is most optimally done at the point of creation in the correct context. This issue requests a new helper method that can be used to ensure and/or correct PIPs that do not have this flag set properly with the expense of O(n), where n is the number of PIPs on the net.The text was updated successfully, but these errors were encountered: