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

Resizing Problems #5577

Open
4 of 15 tasks
AcKoucher opened this issue Aug 14, 2024 · 0 comments
Open
4 of 15 tasks

Resizing Problems #5577

AcKoucher opened this issue Aug 14, 2024 · 0 comments
Assignees
Labels
rsz Resizer

Comments

@AcKoucher
Copy link
Contributor

AcKoucher commented Aug 14, 2024

Description

Currently, RepairDesign uses a strategy of resizing cells to a target slew in order to perform Post Placement Optimization. With the current methodology, the Resizer ends up "fixing" things that are not actually violations of any rule leading to over-sizing.

Note: The API that resizes to the target slew is also used in RepairSetup and RepairHold.

(Some) Current Problems

  • Cells are resized regardless of violations (No DRC, Setup/Hold violations)
  • FFs are being touched.
  • Special cells are also touched. They should be checked with the cell footprint.
  • Clock buffers are used for data network.

Suggested Solution: Enhancement Plan

Phase 1

Phase 2

  • Add FO4
    • Gates that don't respect FO4 should be resized.
    • Gates with cap ratio that don't violate FO4 shouldn't be further sized
  • Redo repair_design sizing using FO4
    • Do sequential sizing based on area increase (nominal buffer area threshold)

Phase 3

  • Remove target slew resizing from setup fixing
  • Remove target slew resizing from hold fixing
  • Make setup fixing or power recovery with global sizing

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rsz Resizer
Projects
None yet
Development

No branches or pull requests

1 participant