-
Notifications
You must be signed in to change notification settings - Fork 577
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
Improve error message [ERROR GPL-0305] RePlAce diverged at newStepLength. #6323
Comments
I heard a remark that a CPU is ca. 1 cycle wide, which is what I wanted to explore a bit out of curiosity. Not related to this issue as such, but I reduced the width and I got a result. There is a single wire running across, every 150um or so, there is a buffer and from the timing report, I see something like 50ps per 150um. 430um across. so 50ps * 3 (ca. 430 / 150um is roughly 3), is 150ps. The actual arrival time was 190ps for the worst path. So 33ps per 100um. megaboom is ca. 1000x1000um (or should be, not quite there yet). 10 * 33ps = 333ps = 3GHz, which is roughly commercial speeds for such a part. So the "a CPU is one cycle wide" remark is plausible in a very approximate sense. |
Hi @oharboe, this is where the error report comes from: I would say this is more then a divergence, it is an actual crash because newStepLength was calculated as NAN or infinity. I will investigate why. Also, I think changing the wording for this report is necessary, since it is an actual crash. |
@oharboe would you happen to know why I was not able to run your issue with debug mode? Furthermore, I noticed that gpl never converged to the 0.10 overflow, I want to investigate that. |
Don't know. Sorry. |
Using a lower density such as 0.10, gpl converges. I believe we get stuck in 0.67 overflow when using 0.40 density, as provided by Oyvind, because of the bin area scaling in line OpenROAD/src/gpl/src/nesterovBase.cpp Line 892 in 5daa1de
I wonder how we could avoid this issue while still making it work with a 0.40 density. My understanding is that a lower actual density than the target density should still be acceptable. |
I encountered the same message #6338. It takes me some times that the density was too high as the message is not very straigtforwad. |
Description
I wanted to have a look at what happens when there are long wires to distribute a signal, so I created a pathological case:
However, I get a mysterious error message in global placement.
I think global placement wants me to tweak some variable or other, but the error message doesn't give me a clue what to fix.
untar and run global_place_skip_io_Bus_asap7_766_2024-12-07_15-05.tar.gz
Suggested Solution
Make the global placement work or make the error message actionable.
Additional Context
No response
The text was updated successfully, but these errors were encountered: