Closed bmentink closed 6 years ago
Verilator version?
Right.. seems most likely.
My Verilator is 3.856 and after the build I get:
$ grep __DOT__ram_prog verilator/obj_dir/Vj1a.h
VL_SIG16(v__DOT__ram_prog[4096],15,0);
The version giving the error is:
Verilator 3.886 2016-07-30 rev verilator_3_884-13-gb4a7e46
The grep above gives "VL_SIG16(j1aDOTram_prog[4096],15,0);"
Can I give an other help?
Mine's Verilator 3.856 2014-03-11 rev verilator_3_855-19-g749ff02 Which works. If you're on debian you can downgrade to it - I'm just using the prebuilt version ubuntu/debian has. Possibly worth raising as a regression bug against Verilator - since the newer version breaks our code.
On Mon, Oct 17, 2016 at 8:23 AM, bmentink notifications@github.com wrote:
Can I give an other help?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jamesbowman/swapforth/issues/43#issuecomment-254075987, or mute the thread https://github.com/notifications/unsubscribe-auth/AO8-GIKedsskY7KlwWpOCeHxs53JhxMGks5q0pW9gaJpZM4KVMeZ .
-- Remy
There is a way to get the old naming back: just add an option --l2-name v
to verilator. Did not try with the older versions though.
Just tried it with my old Verilator (3.856):
%Error: Invalid Option: --l2-name
Looks like this changed in 3.884:
I tried running "make bootstrap" for j1a .. but it fails ..