Closed sifferman closed 7 months ago
Could the issue be with default/patches/verilated.mk.in? Although it looks like it's only being applied for Darwin releases, so I don't know why the Linux release would be affected
Maybe this commit was what broke things: verilator/verilator 8b44a54b
Yes. I tried building Verilator but with verilator/verilator/include/verilated.mk.in replaced with YosysHQ/oss-cad-suite-build/default/patches/verilated.mk.in, and the error ("the coroutine header requires -fcoroutines") was replicated.
I believe removing the patch file will correct the error.
Alright, this is the commit that broke things:
< _MY_CXX_CHECK_IFELSE( < -fcoroutines-ts, < [CFG_CXXFLAGS_COROUTINES="-fcoroutines-ts"], < [CFG_CXXFLAGS_COROUTINES="-fcoroutines"]) --- > _MY_CXX_CHECK_SET(CFG_CXXFLAGS_COROUTINES,-fcoroutines-ts) > _MY_CXX_CHECK_SET(CFG_CXXFLAGS_COROUTINES,-fcoroutines) > _MY_CXX_CHECK_SET(CFG_CXXFLAGS_COROUTINES,-fcoroutines-ts -Wno-deprecated-experimental-coroutine)
Verilator used to always include -fcoroutines
by default, but now it only includes -fcoroutines
if it is supported.
I believe that the error is because OSS CAD Suite builds Verilator with a C++ compiler that does not support coroutines. This can be corrected building Verilator with >=g++10
Thanks for looking into this issue. This is generaly hard to support on multiple linux distributions way we are building it, since it will always be affected by compiler on host machine as well.
Anyway I am in process of updating base OS docker image, but it will take some time.
Would it be possible to just do a hotfix until the OS docker image is updated? I could throw together a patch if that would be helpful
@sifferman sure. please do. Will be happy to try it out
Starting with release 2023-10-21, the Verilator binary gives the error "the coroutine header requires -fcoroutines". There is no error if I build from master.
System Info
Test
Full Error