DenseChip

Synthesis & Logic Optimization · All levels

PD Handoff Reports: Step-by-Step Walkthrough

Step-by-Step Walkthrough for PD Handoff Reports.

Step-by-step analysis walkthrough

Use when you own PD Handoff Reports in a synthesis closure review.

  1. Confirm exact run context (RTL/SDC/lib/switch set).

  2. Open section QoR dashboard and identify first drift.

  3. Inspect topic-level report for mechanism evidence.

  4. Determine owner and candidate reversible action.

  5. Apply one change only; avoid bundled fixes.

  6. Run full timing/area/power checks.

  7. Validate side effects on neighboring path groups.

  8. Publish memo with outcome and residual risk.

Artifacts to collect

  • handoff manifest, baseline QoR snapshot, assumption checklist

  • QoR dashboard

  • run manifest

  • constraint diff

  • regression matrix

Decision memo template

diagram
SYNTHESIS DECISION MEMO — PD Handoff Reports
run context:
observed metric:
hypothesis:
fix:
regression:
owners: synthesis lead, PD lead, CAD owner

Reference visuals

PD handoff package

diagram
netlist + SDC + scenario map
QoR baseline + assumptions
owner matrix + known risks

Synthesis deep dive

Physical-aware synthesis reduces logic-to-route surprise when correlation is monitored.

Concept diagram

diagram
PHYSICAL-AWARE LOOP

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

Metric graph

diagram
CORRELATION DELTA

logic view WNS      ███████
topo view WNS       █████
route trial WNS     ████

Reports and artifacts

  • topo QoR

  • congestion heatmap

  • handoff manifest

  • delta compare vs PD

Mini case study

Topo compile looked clean, but hotspot congestion predicted route failure and prevented late ECO churn.

Debug branches

  • Check hotspot ownership

  • Bound correlation drift

  • Escalate if handoff assumptions stale

Senior review question

Ask: what evidence proves this QoR move is real and stable?

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.

Principal synthesis review addendum

Strong handoff packages constraints, scenario assumptions, and QoR baselines so PD can preserve intent and diagnose deltas quickly.

Metric: handoff completeness, view consistency, first-route QoR deviation

Practice this lesson