A view is named FUNC_SS_RCMAX, but its actual configured objects point to an FF library and a different RC condition. What does the timing engine use?
From PDVerse MMMC Interview Masterclass · pdVerse Mentor Series
Direct answer
The configured object associations — not the human-readable name. The engine doesn't parse the name string for meaning; it uses whatever library, RC corner, and constraint mode are actually attached to that view object.
Mentor explanation
Names exist for engineers, not for the analysis engine. A name like FUNC_SS_RCMAX is a convenience — a hint meant to help a human quickly recall what a view is supposed to represent. But naming a view correctly and configuring it correctly are two separate actions, and nothing in the tool enforces that they stay in sync. If someone renames an object, copies a script and forgets to update an association, or reuses a delay corner by mistake, the name becomes actively misleading while the underlying analysis proceeds exactly as configured — silently, with no error. Never take a name as proof. Trace the actual object references before trusting what a view represents.
Tool check
report_analysis_views (or scenario inventory report)Inspect attached library set, RC corner, and constraint mode rather than trusting the name.
Key takeaways
- The configured object associations — not the human-readable name.
- The engine doesn't parse the name string for meaning; it uses whatever library, RC corner, and constraint mode are actually attached to that view object.
Self-check: can you answer this aloud?
Try a 45-second answer using this structure:
- State the direct answer.
- Explain the timing or physical reason.
- Name one caveat.
- Say how you would verify it in a real flow.
Continue learning free
Get a practical low-power chapter
Receive the existing “Low Power and Multivoltage Fundamentals” PDF chapter and its download link by email.
Keep connecting concepts