Scenario: QoR Storm: Theory Deep Dive

Foundational theory

Scenario: QoR Storm is a core part of Synthesis Interview Prep. QoR storms test run-hygiene fundamentals: constraint diffs, library updates, and compile switches before speculative ECO. Senior synthesis engineers connect every QoR claim to constraint context, compile setup, and reproducible artifacts.

Core concepts explained

• QoR storms test run-hygiene fundamentals: constraint diffs, library updates, and compile switches before speculative ECO.

• Primary metric: overnight WNS/TNS regression with no RTL intent change

• Primary artifact: scenario brief, run manifest diff, triage timeline

• Owners: synthesis lead, STA owner, CAD owner

• Compare timing, area, and power together

• Preserve run manifest for every regression jump

Why this matters at closure

At tapeout pace, Scenario: QoR Storm decisions can either shorten closure loops or create hidden debt. Senior synthesis interviews reward mechanism-first QoR reasoning under uncertainty.

Mental model

overnight regression
  -> manifest diff
  -> isolate first drift
  -> reversible fix

Worked intuition

1. Freeze RTL tag, constraint tag, and compile switches.

2. Open overnight WNS/TNS regression with no RTL intent change and isolate the first meaningful regression.

3. Classify whether issue is constraints, mapping transform, or physical estimate.

4. Collect scenario brief, run manifest diff, triage timeline and owner signoff evidence.

5. Pick minimal reversible fix and define rollback criteria.

6. Run timing + power + area regression matrix before merge.

Common misconceptions

• Better WNS always means better overall QoR.

• dont_touch is harmless if timing still passes.

• Retiming gain is free and always safe for formal.

• Topographical estimates are equivalent to signoff route outcomes.

Visual reinforcement

QoR storm triage board

overnight regression
  -> manifest diff
  -> isolate first drift
  -> reversible fix

Layer responsibilities

SYNTHESIS OWNERSHIP LAYERS — Scenario: QoR Storm

layer               owns                          failure mode
----------------    ---------------------------   -------------------------
constraints         clocks/exceptions/policy      fake QoR optimism
mapping             cell choices/structure        depth/fanout regressions
optimization        timing/power tradeoffs        one-metric overfitting
physical-aware      topo/congestion estimates     handoff delta surprises
closure             ECO order/regression          fixes break other corners

Synthesis deep dive

Interview readiness comes from repeatable QoR reasoning under pressure.

Concept diagram

INTERVIEW ANSWER SHAPE

context -> metric -> mechanism -> fix -> regression -> ownership

Metric graph

PANEL SCORING

clarity      ███████
mechanism    ██████
regression   █████

Reports and artifacts

• mock scorecard

• scenario debrief

• Q&A coverage

• framework adherence

Mini case study

Candidate improved by replacing tool-command answers with evidence-driven closure narratives.

Debug branches

• State assumptions first

• Defend option tradeoffs

• Close with rollback/regression

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.

Theory reinforcement

Senior synthesis interviews reward mechanism-first QoR reasoning under uncertainty.