Closed rodrigomelo9 closed 4 years ago
That was a puzzle, and I think you may have indirectly found a Verilator bug! (I specify 1364-2001 as the language standard, but that code passed linting.) Fixed, and I'll raise an issue on the Verilator repo. Thanks!
Take into account that it was a complaint of iverilog (Icarus Verilog), not the Verilator linter.
Yes, I saw. I think Verilator is wrong here, since that code wasn't legal Verilog-2001, but legal Verilog-2005/SystemVerilog. I check my code with Verilator, so it should have caught this.
The last complaints of iVerilog (over two files):