Geoffrey Coram

OpenVAF crash when compiling

2

The attached Verilog-A module caused OpenVAF to crash and produce the attached log file. Note that this module does have a declared parameter, so it's not the same issue as...

incorrect $mfactor scaling for potential noise contributions

8

If one has V(out)

Fix for crash when compiling module with no parameters.

4

See https://github.com/pascalkuthe/OpenVAF/issues/103

macro call parsing issue

2

If I have \`define myexp exp and then call it with y = \`myexp(5.0); OpenVAF complains error: argument mismatch expected 0 but found 1! If I do y = \`myexp...

Add support for `undef

3

[root@5033e3bcb6f9 io]# target/release/openvaf r3_cmc.va error: macro '`undef' has not been declared --> /io/r3_cmc.va:127:9 | 127 | `undef __VAMS_COMPACT_MODELING__ | ^^^^^^ macro not found here error: unexpected token identifier; expected 'discipline',...

issue with node collapse for non-zero potential contribution

3

The module contrib2 (rename attachment contrib2.txt to contrib2.sp) acts like a 0V voltage source in ngspice-42, even though the contribution is 1.0: V(out,in)

singular matrix with voltage contribution

5

When I have a voltage branch contribution that connects implicitly to ground: V(a)

support range for string parameters

2

error: unexpected token ''{'; expected '(', ''{', system function identifier, identifier, literal, '~', '!', '+' or '-' --> /home/gjcoram/modeling/cmc_qa/cmcqa/model_qa/veriloga/vacode/param_example2.va:18:36 | 18 | parameter string type = "NPN" from '{ "NPN",...

But $ceil() is, and both floor() and $floor() are supported.

If you don't specify a limiting function (either a "string" for a built-in or an analog function identifier), then openvaf will crash when compiling the module. The problem is this...