chipsalliance
Remove lowRISC/Ibex?
The ibex test is broken due to using old c++11, and has been for years. The repo for Ibex hasn't been updated since 2019, and the test was only ever runnable against verilator, slang, and circt-verilog.
So, shall we remove it, or is someone willing to repair it (it needs to be C++14 at least for Verilator but better to use C++20)?
CC @wtatarski as I think you added this runner, and CC @tgorochowik
I think it would be nice to maintain the ibex core. If you cannot find someone, I can ask the lowrisc people to see if this can be fixed.
If you could ask them to fix & watch it occasionally IMO that would be perfect arrangement.
@vogelpi @Razer6 is this something the ibex team would be interested in fixing? I would love to have ibex coverage on sv-tests being maintained, especially as we are currently expanding circt_verilog with ibex in mind.
Thanks for pinging me @tobiasgrosser . Would you mind elaborating a bit on what you would like us to fix / maintain please? I am happy to raise this internally with the team but the initial description above isn't fully clear to me. If you prefer, you can also send me an email please. Thank you.
Ibex cannot be bumped automatically because the FPGA synth example has been moved to a separate repo. So fusesoc has to be pointed there instead of the actual Ibex repo. I guess we can replace the Ibex submodule with that?
@kbieganski thank you for the pointer. This seems to be different to the C++ concern mentioned in the initial issue.
@vogelpi, the task is currently slightly underspecified. Or rather, it seems someone needs to investigate why ibex is currently failing in the chipsalliance sv-test setup and how this can be fixed. I pinged you as I felt ibex coverage in this repo has value, so had hoped lowrisc can look into this. I will see if I can get further information for you.
@kbieganski thank you for the pointer. This seems to be different to the C++ concern mentioned in the initial issue.
It's connected. We haven't updated Ibex in years (because of what I said) and this old version uses compiler flags that aren't supported by current Verilator.