J1B does not compile with the newest Verilator 4.210 2021-07-07 rev v4.210-19-gde408a5e · Issue #72 · jamesbowman/swapforth · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to compile J1B (via make in j1b/swapforth/j1b/verilator), I get the old error:
verilator --l2-name v -Wall -I../verilog/ --cc j1b.v ../verilog/j1.v ../verilog/stack.v --top-module j1b --exe sim_main.cpp
%Error: j1b.v:63:8: Duplicate declaration of signal: 'uart0_wr'
: ... note: ANSI ports must have type declared with the I/O (IEEE 1800-2017 23.2.2.2)
63 | wire uart0_wr = io_wr_ & io_addr_[12];
| ^~~~~~~~
j1b.v:8:24: ... Location of original declaration
8 | output wire uart0_wr,
| ^~~~~~~~
%Error: j1b.v:64:8: Duplicate declaration of signal: 'uart0_rd'
64 | wire uart0_rd = io_rd_ & io_addr_[12];
| ^~~~~~~~
j1b.v:9:24: ... Location of original declaration
9 | output wire uart0_rd,
| ^~~~~~~~
%Error: Exiting due to 2 error(s)
make: *** [Makefile:8: obj_dir/Vj1b] Error 1
it can be easily fixed as described in #67 - there is a commit wzab@4a705b0 that can be cherry-picked to fix it.
Afterwards the J1B builds with Verilator 4.038, but an attempt to build it with 4.210 still leads to an error:
It seems that using the Verilator has significantly changed between the versions 4.038 and 4.210.
This is a comparison of a single example file: verilator/verilator@v4.038...v4.210 . You can scroll down and load the diff for the examples/make_tracing_c/sim_main.cpp .
Uh oh!
There was an error while loading. Please reload this page.
When I try to compile J1B (via
make
inj1b/swapforth/j1b/verilator
), I get the old error:it can be easily fixed as described in #67 - there is a commit wzab@4a705b0 that can be cherry-picked to fix it.
Afterwards the J1B builds with Verilator 4.038, but an attempt to build it with 4.210 still leads to an error:
The
l2-name
option does not help. Inspection of files generated in obj_dir shows that t he whole class structure has changed.The text was updated successfully, but these errors were encountered: