Skip to content

Regression test to check incremental timing analysis results/qor match full timing analysis during optimization #1310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vaughnbetz opened this issue May 21, 2020 · 5 comments
Assignees
Labels
VPR VPR FPGA Placement & Routing Tool

Comments

@vaughnbetz
Copy link
Contributor

Proposed Behaviour

We now have an incremental STA mode that is much faster for small changes in the optimizers. To confirm it always gets the same results as the full timing analysis, we should have one or two regtests on small circuits that check that we get the same results (should be identical placement output file, and identical routing output file) with incremental vs. full static timing analysis guiding the optimizers.

I think the best regtest would be two circuits, on the flagship architecture (https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/master/vtr_flow/arch/timing/k6_frac_N10_frac_chain_mem32K_40nm.xml).
Suggested circuits:
or1200.v (small, good for a quick test, put in vtr_reg_strong)
LU8PEEng.v (bigger, tests more blocks, put in vtr_reg_nightly)
Both are in https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/master/vtr_flow/benchmarks/verilog/LU8PEEng.v

The VTR developer guide has information on how to create a regtest, and starting with an existing regtest as a template would be a good idea. See https://docs.verilogtorouting.org/en/latest/dev/developing/#adding-tests

@vaughnbetz vaughnbetz added the VPR VPR FPGA Placement & Routing Tool label May 21, 2020
Copy link

github-actions bot commented May 4, 2025

This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment.

@github-actions github-actions bot added the Stale label May 4, 2025
Copy link

This issue has been marked stale for 15 days and has been automatically closed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2025
@vaughnbetz
Copy link
Contributor Author

We do check this now, using the "-check_incremental_sta_consistency" option to a task. Looking at the tests, they look pretty compete except I think it would be good to have a test with the multiclock circuit that uses an sdc. Sending to Alex to see if he can do that. We can just make a new test that runs that one circuit with this option.

@AlexandreSinger
Copy link
Contributor

PR #3058 has been raised to add this extra test @vaughnbetz

@vaughnbetz
Copy link
Contributor Author

Great, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
VPR VPR FPGA Placement & Routing Tool
Projects
None yet
Development

No branches or pull requests

2 participants