ID 683283
Date 9/24/2018
Public

## 2.7.2.1. Example Step 2—Partition Designer Creates .sdc with Partition-Specific Constraints

The partition designer compiles the design with the .sdc with project-wide constraints and might want to add some additional constraints. In this example, the designer realizes that he or she must specify a false path between the register called reg_in_1 and all destinations in this design block with the wildcard character (such as ” * ”). This constraint applies entirely within the partition and must be exported to the top-level design, so it qualifies for inclusion in the .sdc with partition-specific constraints. The designer first defines the module_A_hierarchy variable and uses it when writing the constraint as follows:
if {![info exists module_A_hierarchy]} { 	set module_A_hierarchy "" }  set_false_path -from [get_registers ${module_A_hierarchy}reg_in_1] \ -to [get_registers${module_A_hierarchy}*]