Redirected netSet Property Creation and Optimization
While creating the supply connectivity across the design hierarchy, there could be conflicts where the same net expression property gets resolved to different supply nets at the top. For correct supply connectivity resolution in such scenarios, a redirecting netSet property is created and an optimization algorithm is executed to ensure that the redirection of netSet property happens across the design hierarchy only where required. Redirection is done where having a pure global net expression can cause issues in the supply connectivity across the design hierarchy. This ensures minimum number of netSet properties at the top instance.
Wherever the property name is created, the prefix is added as mentioned in the setup to identify various pg_type. Redirected property name is realized as [@Prefix_cellname_count:%:topsuplyname!]. The illustration below represents the creation of redirected netSet property in the design.
In a design if there is a hierarchy and no Liberty stop cell, Power Manager traverses to the level where net expressions exist. Or, if the net expressions are already redirected to have different property names, it is the reference for the tool to make the connectivity.
Related Topics
Handling of Low Power Special Cells
Support of Hierarchical 1801 for Import Flow
Removing Imported Power Intent
Return to top