From: <bo...@el...> - 2020-06-15 13:44:02
|
Cary R. via Iverilog-devel writes: > Hi Uwe, > > Any of the following should work: -g2005-sv, -g2009, -g2012, -g2017 to tell > iverilog to process the files as SystemVerilog using the appropriate keywords. > > We support both array declaration styles: > > logic mdarr [0:3][0:7]; > or > logic mdarr [4][8]; > > I ran a quick test example and it works. I believe we do not currently support > passing arrays as arguments, array patterns, array slices, etc., but the basic > support is there. > Hi Carry, sorry for not getting back earlier, I has a long weekend ;-) Probably my question was not clear. I meant to put the Verilog language generation selection into a cmd file like: ==== llbbc_reg.cmd ==== +libdir+. +libdir+../avr_if +libext+.v -g2012 llbbc_reg_tb.v and call it like "iverilog -c llbbc_reg.cmd" This results in > iverilog -c llbbc_reg.cmd Error: unable to parse line 4 in llbbc_reg.cmd. iverilog: parsing failed in base command file llbbc_reg.cmd. Only by omitting the -g line in the command line and calling "iverilog -c llbbc_reg.cmd -g2012" iverilog compiles. My question was: Is there any syntax to put things like the "-g2012" argument in the command file, so I do not have to specify it on the command line? Bye -- Uwe Bonnes bo...@el... Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 --------- |