Open eder-matheus opened 3 months ago
This is similar to: https://github.com/The-OpenROAD-Project/OpenROAD/issues/5305
I think the better solution would be to figure out why DRT is generating so many shorts as the starting point.
@gadfort For both designs, the problem seems to be the route guides generated by GRT. We were using very low resource adjustments (20%) for these designs, and when I increased it to 40%, both sky130hd/aes and sky130hs/riscv32i finished in less than 20 iterations.
What happens is that when using very low reduction values, GRT assigns too many nets to the same region, which can make DRT struggle to find a clean solution. I'm investigating how to turn GRT smarter about the resources available, in parallel to understanding if it's possible to detect if a design can't be routed without DRCs.
@eder-matheus is it possible the original resources are not getting computed correctly? If I don't apply any reductions, I would assume the capacities reported should reflect the number of tracks available.
In the image below, you can see the capacity (20) is reported for the GCell (it's hard to see the outline), but if I count the number of resources it's 16 if I exclude the tracks that are inside the power rails, in this cell, global routing is using 17 resources which might be contributing to the issue.
It looks like GRT should be derating the power, but this appears to not be the case here.
@gadfort If I remember correctly, the Capacity shown in the GUI is the first computed (i.e., it considers all the resources calculated before any reduction). The usage would include the reductions from blockages and user-defined adjustments and the routing. I'll double-check if that is the case.
@gadfort If I remember correctly, the Capacity shown in the GUI is the first computed (i.e., it considers all the resources calculated before any reduction). The usage would include the reductions from blockages and user-defined adjustments and the routing. I'll double-check if that is the case.
That's how it works. I load the design without running the routing, and it shows what I described: the capacity is the full resources calculated at first, and the reductions from blockages are shown in the usage.
@eder-matheus ahh, okay. thanks for checking on that
grt needs to be a lot less optimistic about routing resources … see https://github.com/The-OpenROAD-Project/OpenROAD/issues/5061
@eder-matheus just updating the routing resources per design doesn't seem that viable and overall is a sub-par solution. Now that your CI is down to 9 minutes, how are you going to track the improvements made here?
@eder-matheus just updating the routing resources per design doesn't seem that viable and overall is a sub-par solution. Now that your CI is down to 9 minutes, how are you going to track the improvements made here?
In this issue, we have a test case where the vast number of shorts still happens. I also found the files for an old run (before my update in the routing resources) for sky130hd/aes, which takes almost two hours only in DRT. It's available here: https://drive.google.com/file/d/1DdmM-jvEBQU2zW74LxlAi9veSflmJj12/view?usp=sharing.
And I agree there are better solutions than updating the config files per design. I had to make this change for sky130hd/aes to have an important PR merged, but GRT should be more intelligent in how it handles congestion without user input.
@gadfort FYI, I created this issue to track the necessary GRT enhancement regarding routing resource adjustments: https://github.com/The-OpenROAD-Project/OpenROAD/issues/5423.
Describe the bug
From https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/pull/2142, sky130hs/riscv32i has a huge runtime after the changes during synthesis. It happens due to a bad routing resources configuration, leading to many wires assigned to a congested region. DRT takes more than half of the iterations trying to solve 36 violations that look unsolvable.
Expected Behavior
DRT should give up on hopeless designs.
Environment
To Reproduce
Test case available here: https://drive.google.com/file/d/1c7lxyFGMgj7dW62qUXk2nnEbXUs1-IAF/view?usp=sharing Another case where DRT struggles with lots of DRCs (specifically shorts): https://drive.google.com/file/d/1DdmM-jvEBQU2zW74LxlAi9veSflmJj12/view?usp=sharing
Relevant log output
No response
Screenshots
No response
Additional Context
No response