dual clock sdc exist, causing TCLCMD-1594 error - #904
Merged
Conversation
harrisonliew
approved these changes
Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related PRs / Issues
Type of change:
Impact:
Contributor Checklist:
masteras the base branch?poetry.lockfile if you updated the requirements inpyproject.toml?e2e/if this feature depends on updated plugins?Fix duplicate create_clock warning in PAR (TCLCMD-1594/958)
When a post-synthesis SDC (gcd.mapped.sdc) is present, Hammer's MMMC script loaded both clock_constraints_fragment.sdc (generated from vlsi.inputs.clocks) and the synthesis SDC, both of which define create_clock for the same clock. This caused Innovus to warn that the clock definition was being overwritten.
Fix: in generate_mmmc_script(), filter out clock_constraints_fragment.sdc from the SDC list when a post-synthesis SDC is present, since the synthesis SDC already carries the clock definition. The pin constraints fragment is still included. Behavior is unchanged when no post-synthesis SDC exists (e.g. running PAR standalone).