--- Quote Start ---
This example compiles without a warning and I get the following worst-case tpd - 63,104ns. However, as soon as I add subtraction, the tool cannot provide me with this info because it thinks that the output is not connected to the inputs.
--- Quote End ---
I still get the same warning with the new architecture code. (Quartus 9.0, Classical Timing Analyzer, Cyclone III).
--- Quote Start ---
Warning: No paths found for timing analysis
--- Quote End ---
You'll notice that you aren't able to define "Read_Write" as a clock, neither in Classical Analyzer nor Time Quest, apparently because it's an internal signal of unknown timing. If you make it an external input, timing analysis works.
Honored Contributor
