IntermediateQuestion 36 of 222

What should be reviewed after read_sdc applies a file?

From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide

Short Answer

Parsing success is the first gate, not the finish line — an SDC file with zero syntax errors can still leave the design under-constrained or misconstrained. Review the errors and warnings first, then dig into the object-resolution messages specifically — those tell you whether every get_pins/get_clocks-style selector actually found real objects, or silently matched nothing.

Technical Reference DiagramWhat should be reviewed after read_sdc applies a file?

Technical Explanation

  • Check for overridden constraints too — a later command in the file (or a later file) can quietly replace an earlier constraint without any error being raised.
  • "

What To Check

  • Warning sign: The SDC applies with empty selectors or replaces an earlier clock unexpectedly.
  • Inspect: Compare one named object across the related reports; the same object should tell a consistent story.
  • Correct: Fix the source SDC or load context, reopen a clean checkpoint, and reapply once.

Command Checks & Actions

  • read_sdc <file.sdc>: parses or applies the timing constraints
  • report_clocks: shows clock definitions and relationships
  • report_exceptions: shows timing exceptions and their scope

Run the commands in order. Each line answers a separate part of the check.

Healthy, Suspicious & Hard-stop Results

  • Expected: Review errors, warnings, object-resolution messages, overridden constraints, current context, and resulting reports; parsing success is only the first gate.
  • Stop before floorplanning when required logic or timing coverage is missing or unexplained.

Common Mistake

The Trap: Do not assume the check passed just because ICC2 continued. Fix or narrowly justify the named objects, then rerun the same command.

What The Interviewer Is Testing

Be ready to explain why this matters before floorplanning.

Follow-up Question & Model Response

Model response: “I would save the report, inspect one affected object in the correct block and scenario, and make or request this correction. ”

Physical Design & Planning Handbook

Dive into 14 comprehensive chapters covering netlist sanity, FinFET grids, macro placement, power grids, CTS, and timing budgeting.

Offline PDF Bundle

Want all 1109 questions offline?

Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.

See what's inside the bundle
Timing Constraints (SDC) Handbook — nine chaptersSDC ConstraintsNine chapters on clocks, exceptions, and constraint linting.