Stefan Wallentowitz

I have a few more as I worked a lot on fixing this in wavedrompy. They are from my regressions (https://github.com/wallento/wavedrompy/blob/master/test/regressions.py#L85) ## `10` ``` { "signal": [ { "name": "sig",...

Yeah, I skipped through them. My gut feeling is that half of them are solved easily within an hour (hidden names, widths, etc.)

That is not what this PR is about, to be frank. At the moment you are suppressing warnings at simulation build. A linter flow will help improve the code quality...

Sorry, @agrobman, but you clearly miss the point. It has nothing to do with SV compliance. If you have any problem with the synthesizable part of SV not working with...

@aprnath thanks, just drop me a mail if you have any questions or want to discuss it in general. @agrobman Verilator 4.036. It is based on our docker image (2020.06-rc2,...

From https://github.com/verilator/verilator/issues/2433 where @agrobman asked: > I don't understand what do you want. > > You started all this complaining that you got a lot of warnings and we don't...

When anyone from your team finds time and patience, I encourage you to post WIDTH warnings here that you believe are entirely wrong or way too pedantic. I will go...

Here is an example for the annotations: https://github.com/wallento/riscv/actions/runs/137172924 At an PR it will put them right to the code changes.

From #367: > Thanks for getting the ball rolling on this @wallento. I've added a few minor comments, and have three big ones: > > 1. A lot of the...

Hi @MikeOpenHWGroup, I have ameneded the PR. The changes of 3 are necessary to make the verilator-model run again. I believe long term it would be more useful to have...