Design constraints that query physical information must rely only on physical constraints
entered manually, not on those added by place-and-route commands. Otherwise, these
constraints appear invalid when reloading a post-implementation DCP. This happens
because the DCP load sequence reads the netlist first, then the constraints, and finally
the physical database. Instead of using physical information, modify the query to depend
on other design object properties such as NAME or
REF_NAME.
Here is an example of a non-recommended constraint that relies on
placement information (LOC):
set_false_path -from [get_cells -quiet -hier -filter {REF_NAME=~FD* && LOC=~BLI_*}]