5.2.5. One Critical Chain per Clock Domain
Hyper-Retiming reports one critical chain per clock domain, except in a special case that Critical Chains in Related Clock Groups describes. If you perform a Fast Forward compile, Hyper-Retiming reports show one critical chain per clock domain per Fast Forward optimization step. Hyper-Retiming does not report multiple critical chains per clock domain, because only one chain is the critical chain.
Review other chains in your design for potential optimization. View other chains in each step of the Fast Forward compilation report. Each step in the report tests a set of changes, such as removing or converting asynchronous clears, and adding pipeline stages. The reports detail the performance, assuming implementation of those changes.
Did you find the information on this page useful?