dbSta: check LEF pins against Liberty#10821
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a new check, LEF/LIB-CHK-012, to verify that LEF signal pins exist in the corresponding Liberty cell. It implements the checkLibertyPinPresence method in IpChecker and adds a new pass/fail regression test check_ip_liberty_pins to validate this functionality. There are no review comments, so I have no feedback to provide.
0da497b to
d34074a
Compare
| LibertyCell* liberty_cell = sta_->getDbNetwork()->findLibertyCell( | ||
| std::string_view(master->getName())); | ||
| if (liberty_cell == nullptr) { | ||
| return; | ||
| } |
There was a problem hiding this comment.
Are you somewhere else checking that the liberty cell isn't missing when expected?
|
Good catch. I updated the checker so Verified on the VM only:
All 75 dbSta test targets passed. |
d34074a to
2af5c83
Compare
Signed-off-by: Naveen Venkat <archgen.guest@nyayanidhi.in>
2af5c83 to
602bee9
Compare
|
Fixed the Clang-Tidy-Bazel include-cleaner failure in VM verification:
|
|
Folded this work into #10820 after the review feedback to keep Liberty presence and direction validation in one traversal. Closing this duplicate so the remaining review stays in one PR. |
Summary
LEF/LIB-CHK-012to warn when a LEF non-supply pin is missing from the matching Liberty cellRelated to #4872.
Tests
git diff --checkbazelisk build --jobs=4 --local_cpu_resources=4 //src/dbSta:IpCheckerbazelisk test --jobs=4 --local_cpu_resources=4 //src/dbSta/test:check_ip_liberty_pins-tcl_teston the Ubuntu 22.04 GCP VM fails before test execution while linkingopenroadwith unresolved__isoc23_*glibc symbols from the Bazel LLVM/sysroot toolchain.