Skip to content

Add independent --analysis stage #154

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
kmurray opened this issue Jul 20, 2016 · 2 comments
Closed

Add independent --analysis stage #154

kmurray opened this issue Jul 20, 2016 · 2 comments
Labels
enhancement Feature enhancement VPR VPR FPGA Placement & Routing Tool

Comments

@kmurray
Copy link
Contributor

kmurray commented Jul 20, 2016

Currently the only way to re-do analysis (timing, power, area etc.) is to re-run the routing stage. However this may cause the routing implementation to change.

We should add support for performing analysis independently of routing. This would involve:

  • Adding an --analysis option to control running analysis (similar to --pack/--place/--route)
  • Separating the analysis code from routing
  • Adding support for reading in the .route file produced by the routing stage
This was referenced Jul 20, 2016
@kmurray kmurray added enhancement Feature enhancement VPR VPR FPGA Placement & Routing Tool labels Jul 20, 2016
@kmurray
Copy link
Contributor Author

kmurray commented Mar 8, 2017

As of ca8f27f VPR supports the --analysis option.

However VPR currently does not re-load the routing (from the .route file), so at the moment routing must still be performed before doing analysis.

@kmurray
Copy link
Contributor Author

kmurray commented Jul 20, 2017

As of 8fe7c1e VPR supports re-loading routing (thanks to @wjiamin).

So the --analysis option should now works as desired.

@kmurray kmurray closed this as completed Jul 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature enhancement VPR VPR FPGA Placement & Routing Tool
Projects
None yet
Development

No branches or pull requests

1 participant