Skip to content
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

Make latch_map_file truly optional #869

Merged
merged 1 commit into from
Jun 27, 2024
Merged

Make latch_map_file truly optional #869

merged 1 commit into from
Jun 27, 2024

Conversation

edwardcwang
Copy link
Member

Right now if a technology doesn't specify the latch map file, "techmap -map None" is written into the generated tcl.

Type of change: Bugfix

Impact: Change to a Hammer plugin

Contributor Checklist:

  • Did you set master as the base branch?
  • Did you state the type-of-change/impact?
  • Did you delete any extraneous prints/debugging code?
  • (If applicable) Did you add documentation for the feature?
  • (If applicable) Did you update the poetry.lock file if you updated the requirements in pyproject.toml?
  • (If applicable) Did you add a unit test demonstrating the PR?
  • (If applicable) Did you run this through the e2e integration tests?
  • (If applicable) Did you update the submodules in e2e/ if this feature depends on updated plugins?

Right now if a technology doesn't specify the latch map file, "techmap
-map None" is written into the generated tcl.
@edwardcwang edwardcwang added this pull request to the merge queue Jun 27, 2024
Merged via the queue into master with commit eb86e88 Jun 27, 2024
4 checks passed
@edwardcwang edwardcwang deleted the yosyslatchmap branch June 27, 2024 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants