Verilog Parser features required to parse Quartus Prime .vo/vqm files

[thunder-hammer]

Currently I only have one example of each of these formats. There could be a lot more constructs than what I see.

VO files

defparam structure
defparam \avs_s1_readdata[12]~output .bus_hold = "false";

constants mapped to ports in instances
cyclonev_io_obuf \avs_s1_readdata[16]~output ( .seriesterminationcontrol(16'b0000000000000000));

the tri1 type

tri1 devclrn;
tri1 devpor;
tri1 devoe;

the tri0 type probably exists too? may as well support it.

! on port mappings within instances.

cyclonev_lcell_comb \ctrl_reg[7]~feeder (
	.dataf(!\avs_s1_writedata[7]~input_o )
	);

VQM files

Everything needed for VO files plus

inverters on assignment statements
assign \fp_pow_0002:fp_pow_inst|__ALT_INV__prodXY_uid496_pT2_uid435_expPolyEval_cma_s[0][49] = ~ \fp_pow_0002:fp_pow_inst|prodXY_uid496_pT2_uid435_expPolyEval_cma_s[0][49] ;

[thunder-hammer]

The tri1 and tri0 types can be maintained like the wire and reg types. The composer needs to be updated to keep track of all these types.

[thunder-hammer]

The defparam should be able to be handled much the same way the current parser currently handles the parameters. Only difference is it may have to create a new instance to add the parameter to first?

[wirthlin]

Note from Andrew:

VQM files are produced by synopsis simplify. The b13 vqm files are linked below (note that GitHub doesn't allow you to attach .vqm files so the extensions were renamed to please GitHub).

b13_2018.vm.txt
b13_2018.vqm.txt
b13_2018.vhm.txt

[thunder-hammer]

Additional constructs found in the .vo format edited into the original issue.