Øyvind Harboe
Øyvind Harboe
Experiment, there's a detectable, but not significant difference https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/pull/2541
I wandered through a couple of the End point Slack Histogram buckets in MegaBoom and it looks like the need for retiming is endemic. This is based purely on finding...
> We should fix the crash but I don't think those flow options are that useful. It was preliminary work on remapping and has never reached maturity. Hopefully with @QuantamHD...
@hzeller @QuantamHD Ideas?
> Perhaps it wants a -latomic in the link opts? https://github.com/hdl/bazel_rules_hdl/blob/main/dependency_support/edu_berkeley_abc/bundled.BUILD.bazel#L1220 Mucked around with that, couldn't get it to work, same linker error. ``` diff --git a/WORKSPACE b/WORKSPACE index 30963dbf73..f58940f2bd...
From copilot: The error indicates that the linker (ld.lld) is unable to resolve the symbol std::__glibcxx_assert_fail, which is part of the GNU C++ Standard Library implementation (libstdc++). This issue typically...
Trying: ``` bazelisk build --cxxopt=-stdlib=libc++ --linkopt=-lc++ -c dbg :openroad ``` Same result: ``` ERROR: /home/oyvind/OpenROAD-flow-scripts/tools/OpenROAD/BUILD.bazel:115:10: Linking openroad failed: (Exit 1): cc_wrapper.sh failed: error executing CppLink command (from target //:openroad) external/toolchains_llvm~~llvm~llvm_toolchain/bin/cc_wrapper.sh...
Pinata programming: this now produces a debug build... https://github.com/The-OpenROAD-Project/OpenROAD/pull/7358
@QuantamHD @maliberty FYI, I get the same problem now with `bazelisk build :openroad`; use-case bisection. This works: ``` bazelisk build --cxxopt=-stdlib=libstdc++ --linkopt=-lstdc++ :openroad ```
@hzeller Any new insights on this one?