Skip to content

Commit 7fb9cb3

Browse files
oharboeclaude
andcommitted
synth: no SYNTH_KEEP_MODULES name check in a partition
A partition of a parallel synthesis (SYNTH_BLACKBOXES set, one run per partition driven by an external orchestrator) loads only its own portion of the design; the kept modules of the other partitions are not in it. The check added in #4745, that every SYNTH_KEEP_MODULES name selects a module, therefore stops such a partition with "SYNTH_KEEP_MODULES: no module <name> in the design". The check now runs only when the whole design is synthesised, where a name that matches nothing is a typo; in a partition a missing name is expected, as it already is for SYNTH_BLACKBOXES. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
1 parent 75cd896 commit 7fb9cb3

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

‎flow/scripts/synth.tcl‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,10 @@ if { [env_var_exists_and_non_empty SYNTH_KEEP_MODULES] } {
8888
# `-module <name>` would error if the module doesn't exist, which
8989
# is why we use bare patterns instead.
9090
select "$module" "$module\\\$*"
91-
if { [string trim [tee -q -s result.string select -list]] eq "" } {
91+
if {
92+
![env_var_exists_and_non_empty SYNTH_BLACKBOXES]
93+
&& [string trim [tee -q -s result.string select -list]] eq ""
94+
} {
9295
error "SYNTH_KEEP_MODULES: no module $module in the design"
9396
}
9497
setattr -mod -set keep_hierarchy 1

0 commit comments

Comments
 (0)