--- Quote Start ---
The Minimum Pulse Width report that should catch that. It may show up in Fmax secondarily, but Fmax wasn't designed to catch anything that wouldn't be caught in another report. More importantly, there are many cases that slack can cover that Fmax can't. Obviously hold violations are a good example, but complex domain crossings are too. I don't mean to argue so much, but I've seen users get in the habit of looking at Fmax and ignoring the other reports, which means they're often not looking at the full analysis. If they use Fmax because they're more comfortable with it and their main problems are within a domain, no problem at all. The main thing is they realize its limitations.
--- Quote End ---
Thanks Rysc. It is ok we are discussing and not arguing.
hold violations are reported as part of restricted fmax (not traditional fmax, purely historical reasons).
io toggle violations and minimum pulse/period violations as well are covered by restricted fmax.
so is fmax itself and any slack in register timing
so "restriced fmax" is final figure of merit.
for multiple clock domain naturally you look at each domain separately.
Honored Contributor
