You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Largest stage determines the functional 'sliced at point' percentage.
Very similar to existing path_delay_cache except with an added 0.75 to name meaning like 'sliced at the 75% point' ~= inverse 1/0.75 = 1.33 stage pipeline
@suarezvictor can be free to experiment with this by running the tool locally - I will try to get generate some cached numbers myself too as I have time
ex.
pipeline_period_cache/vivado/xc7a35ticsg324/syn/BIN_OP_EQ_uint32_t_uint32_t_0.75.delay
Largest stage determines the functional 'sliced at point' percentage.
Very similar to existing path_delay_cache except with an added 0.75 to name meaning like 'sliced at the 75% point' ~= inverse 1/0.75 = 1.33 stage pipeline
I think it helps with faster estimates
#46
And also can help for searching to get to a specific fmax goal
#48
Planned to work well modeling @suarezvictor is doing too
The text was updated successfully, but these errors were encountered: