Skip to content

Post-routing synchronization cannot handle output pins #1578

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
tangxifan opened this issue Oct 27, 2020 · 2 comments
Closed

Post-routing synchronization cannot handle output pins #1578

tangxifan opened this issue Oct 27, 2020 · 2 comments
Labels

Comments

@tangxifan
Copy link
Contributor

tangxifan commented Oct 27, 2020

Post-routing synchronization is under development to update packing results with the net/pin remapping due to routing optimization. However, current fix-up methodology is applicable to the net remapping on input pins. Any remapping on output pins cannot be fixed.

Expected Behaviour

The post-routing synchronization should work for both input/output pins in any pin equivalence type.

Current Behaviour

Current fix-up methodology is applicable to the net remapping on input pins.

Possible Solution

A thorough and clean solution is to run a repack based on previous packing results and current routing results.

  • The pb_graph_node should be re-placed subject to routing results when instance pin equivalence is enabled.
  • A detailed routing inside the blocks should be called to ensure valid local routing results
  • New packing results should be used in timing analyzer.
  • New packing results should be outputted to a .net file

Steps to Reproduce

See the comments and codes in the vpr/src/pack/post_routing_pb_pin_fixup.cpp of the pull request #1355 .

Context

This will cause wrong bitstream generation due to a mismatch between packing results and routing results.

Your Environment

  • VTR revision used: VPR master
  • Operating System and version: CentOS 7
  • Compiler version: gcc-8.4
Copy link

github-actions bot commented May 9, 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 9, 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 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant