Synthesis & Logic Optimization · All levels

Physical-Aware Synthesis: Tricky Q&A

Senior interview and review questions for Physical-Aware Synthesis.

Section Q&A bank

Use these drills after completing all topics in Physical-Aware Synthesis. Answer with run context, metric, mechanism, owner, fix, and regression.

When should you trust topographical WNS less?

diagram

[INT][SYNTH][PHYSICAL-AWARE-SYNTH]

Q: When should you trust topographical WNS less?

A:
When placement assumptions or RC modeling diverge from PD reality; use it for directionality, not unconditional signoff.

FOLLOW-UP TRAP: Treating topo reports as final signoff.

How do congestion metrics change mapping choices?

diagram

[INT][SYNTH][PHYSICAL-AWARE-SYNTH]

Q: How do congestion metrics change mapping choices?

A:
Dense hotspots may favor simpler, less buffer-heavy logic despite local timing gains from aggressive mapping.

FOLLOW-UP TRAP: Ignoring route pressure in compile decisions.

Q&A drill guide

diagram

CONTEXT -> METRIC -> MECHANISM -> FIX -> REGRESSION -> OWNERSHIP

Sketch while answering

diagram

PHYSICAL-AWARE LOOP

topo compile -> congestion hints -> handoff -> PD correlation

Key takeaways

State exact run context (RTL, SDC, libs, switches) with every QoR claim.
Re-run timing, area, and power regressions after each synthesis ECO.

Common pitfalls

Comparing runs with mismatched constraints or library views.
Timing-only fixes that violate power or area budgets.
Skipping equivalence checks after structural changes.

Practice this lesson