When would you actually need irregular global tree synthesis instead of a standard H-tree, and what does "irregular" specifically mean here?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
Irregular global tree synthesis handles non-symmetric, unevenly inserted tap drivers -- floorplan or global-tree complexities that require manual global tree insertion rather than an automated symmetric H-tree. It constructs multilevel, DRC-clean global trees without tight OCV or common-path requirements, using multilevel buffer trees in a non-H-tree style specifically for minimum latency to all tap drivers -- usable at block level or for top-level channel distribution.
Technical Explanation
- Irregular global tree synthesis handles non-symmetric, unevenly inserted tap drivers -- specifically the floorplan or global-tree complexities that require manual global tree insertion rather than relying on an automated symmetric H-tree.
- "Irregular" here means the resulting tree structure is multilevel and DRC-clean, but deliberately NOT H-tree-shaped -- it's built for minimum latency to all tap drivers given their actual (non-symmetric) positions, not for the skew-robustness symmetry an H-tree provides.
- It's usable at block level or for top-level channel distribution -- not limited to one scale of the design.
- The real tradeoff versus a standard H-tree: you give up the process-uniformity-driven skew robustness that comes from H-tree symmetry, in exchange for a structure that can actually accommodate tap drivers wherever the floorplan put them.
Formula Or Decision Rule
Use irregular global tree synthesis when tap driver placement is non-symmetric or unevenly inserted -- floorplan complexity that a standard H-tree's inherent symmetry assumption can't accommodate.
What To Check
- Warning sign: standard H-tree synthesis repeatedly produces poor-quality results (excess levels, DRC issues, or poor latency) on a floorplan with known non-symmetric tap driver placement.
- Inspect: confirm whether the tap driver layout is genuinely non-symmetric -- if so, that's exactly the situation irregular global tree synthesis addresses.
- Correct: switch to irregular global tree synthesis rather than continuing to fight a symmetric H-tree against an inherently non-symmetric floorplan.
Command Checks & Actions
report_global_clock_tree_qor -clock -net <root_net> -type latencyChecks whether an attempted H-tree is actually achieving good latency given the real (non-symmetric) tap positions.
create_clock_driversStill used to insert the tap drivers themselves, regardless of whether the global tree connecting them ends up H-tree-shaped or irregular.
Healthy, Suspicious & Hard-stop Results
- Expected: the global tree structure matches the actual tap driver layout's symmetry (or lack of it), rather than forcing a topology mismatched to the floorplan.
- Investigate: H-tree synthesis quality is repeatedly poor on a design with known floorplan irregularity -- that's a signal to reconsider the topology choice itself, not just retune H-tree parameters further.
- Stop: a floorplan review confirms genuinely non-symmetric, manually-placed tap drivers, but global tree synthesis is still being attempted as a standard H-tree with no plan to switch approaches.
Common Mistake
The Trap: Forcing a standard symmetric H-tree onto a floorplan with genuinely non-symmetric tap driver placement, when irregular global tree synthesis exists specifically for that situation -- fighting the floorplan instead of using the tool built for it.
What The Interviewer Is Testing
Whether you know irregular global tree synthesis exists as a deliberate alternative for non-symmetric floorplans, not just that H-trees are the only global tree option.
Practical Example
Debug Scenario: A block's tap drivers were placed manually to match an irregular floorplan (due to a large embedded macro forcing asymmetric tap positions). Standard H-tree synthesis repeatedly produces excess levels and DRC issues trying to force symmetry onto that layout -- irregular global tree synthesis, built for exactly this non-symmetric case, produces a cleaner multilevel structure instead.
Physical Design & Planning Handbook
Master ASIC Physical Design Planning & Floorplanning
Dive into 14 comprehensive chapters covering netlist sanity, FinFET grids, macro placement, power grids, CTS, and timing budgeting.
Continue practising