Skip to content

Support route constraint. #2233

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

Open
wants to merge 181 commits into
base: master
Choose a base branch
from

Conversation

Tulong4Dev
Copy link
Contributor

@Tulong4Dev Tulong4Dev commented Jan 26, 2023

Description

  • Allow router to route or skip specific signals.

Related Issue

Motivation and Context

  • Allow route constraints applied to specific signals.

How Has This Been Tested?

Types of changes

  • Bug fix (change which fixes an issue)
  • New feature (change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

Yitian4Debug and others added 30 commits June 16, 2022 19:12
@tangxifan
Copy link
Contributor

golden_results.txt

This is what I got through my local run. I think you turned on the VTR_ASSERT_LEVEL=3 which may cause the issues.

@tangxifan
Copy link
Contributor

I think the santizer option is also on. It causes the issue.

Copy link
Contributor

@tangxifan tangxifan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Tulong4Dev Thanks for the contribution. Code changes look good in general. Need some tuning. Open to discussion.

Copy link
Contributor

@tangxifan tangxifan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry. Wrong review conclusion.


/**
* @file
* @brief This file defines the RouteConstraint class.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should have a bigger comment on what this class is for, what it can currently do, what kind of code belongs here (so people know in the future if there is some new feature code that would best be put here), etc.

@vaughnbetz
Copy link
Contributor

@duck2 : can you take a look at the xml parser part of this pull request and give any feedback you think is appropriate? It is building on some of your code.

@github-actions github-actions bot added build Build system external_libs lang-make CMake/Make code libarchfpga Library for handling FPGA Architecture descriptions libvtrutil labels Apr 20, 2023
@tangxifan
Copy link
Contributor

@Tulong4Dev I believe you are merging the codes in openfpga branch to the master in this PR. Please do not do so. You can see the code changes now contains 9k lines. A way to clean up is to create a new branch on your fork which only contains the routing constraint -related code changes.

@vaughnbetz
Copy link
Contributor

@kimiatkh is hoping this one can be merged soon, as she'd like to build some functionality on top of it. @Tulong4Dev : any ETA? If you're around for the VTR meeting this Thursday at 1:30 pm EST, this could be a good topic to discuss if there is some interaction with you and kimia that could help land this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Build system external_libs lang-make CMake/Make code libarchfpga Library for handling FPGA Architecture descriptions libvtrutil VPR VPR FPGA Placement & Routing Tool
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants