Netlist objects with DONT_TOUCH properties can block optimizations that
would otherwise improve design performance. This section of the QoR Assessment report
identifies the objects that have the DONT_TOUCH property set.
The report includes:
- Hierarchical cells
- Leaf cells
- Nets
Figure 1. Netlist Objects with DONT_TOUCH Property
The cause for each setting is also shown.
Note: The
DONT_TOUCH property prevents the tools from
optimizing the associated paths. Vivado might automatically apply this
property through other design attributes. Remove DONT_TOUCH properties
only when appropriate. For example:- The DFX flow uses
DONT_TOUCHto prevent cross-boundary optimization between static and reconfigurable modules. In this case, do not remove the property. - If
DONT_TOUCHwas added throughMARK_DEBUG, it is not critical to the design flow. However, removing it could make the signal unavailable for hardware probing if the tool optimizes it away.