Branch: equivalent-sites #288

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.

Sign up for GitHub

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

Jump to bottom

Closed

4 tasks

acomodi opened this issue Oct 7, 2019 · 2 comments

Labels

wip

Collaborator

acomodi commented Oct 7, 2019

Why did we need this? (what does this change enable us to do)

This branch implements the equivalent sites placement.

What did it change?

It mainly changes the placement algorithm as well as the architecture parser and the pin handlers during all the stages of VPR.

Should it be merged upstream - if not, when can we delete it?

Yes, PR is already open.

What is needed to get this merged / deleted?

Fix regression test and address potential review comments.

is the implementation work to make suitable for merging / deletion completed?
Is there an associated test?
is this currently part of the Conda package?
is this properly cleaned up in our local repositories?

Tracker / branch / PR & other useful links

PR: verilog-to-routing#988
Old PR with some useful comments: verilog-to-routing#559
VtR issue: verilog-to-routing#513

acomodi added the wip label

Collaborator Author

acomodi commented Dec 3, 2019

Equivalent sites now integrates also the wip branch place_constraints to avoid merge conflicts

Collaborator Author

acomodi commented Jan 8, 2020

Closing, as this is currently fully integrated in VTR upstream.

acomodi closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment