Anyone knowledgeable about https://github.com/The-OpenROAD-Project/OpenROAD/issues/1332 ? More specifically why the Docker Openlane seem to not be hitting it (I'm assuming it doesn't since people manage to run it ...), but my local build does ?
m
Matt Liberty
12/22/2021, 7:47 PM
are you building the same commit of OR in both?
t
tnt
12/22/2021, 8:54 PM
No, the OpenLane docker commit segfaults in spdlog for me ... that particular bug seems fixed in newer openroad but then I hit that CTS issue ... and if I try to pull also a newer OpenLane, then I hit yet another crash somewhere else ...
m
Matt Liberty
12/22/2021, 9:23 PM
Things change all the time so different issues can arise. You need to provide a test case for someone to look at in your issue
t
tnt
12/23/2021, 10:03 AM
Pretty sure it's a known issue by now. Analyzing the core file shows that a well pin
VNB
was used as the clock buffer input pin which is obviously wrong. And I seem to see several recent changes in openlane and open_pdks to provide openroad with modified/patches lef files that don't have those pins so as not to trigger that crash.
Now that a
mpw-4
tag has been added, to openlane, I'm updating all the tools (including openroad) and PDK to the commit referenced in that tagged version, hopefully this will yield a combination that doesn't crash.
tnt
12/23/2021, 10:04 AM
Thanks for pointing out the or_issue script though, that seems very useful for the future. Reproducing crash in OR triggered by openlane was always an issue with all the env it sets up ...
Linen is a search-engine friendly community platform. We offer integrations with existing Slack/Discord communities and make those conversations Google-searchable.