Re: gEDA-user: Re: Icarus Verilog PLI example: PLI_INT32 vs static int

2007-04-03 Thread Günter Dannoritzer
Stephen Williams wrote: int is PLI_INT32 in your case. The static part is something else altogether and perhaps more germain to your problem. You don't say what's crashing, Stu's example or mine, etc., so we have very little to go on. Sorry for being so vague. I was more curious about the

gEDA-user: Re: Icarus Verilog PLI example: PLI_INT32 vs static int

2007-04-03 Thread Stephen Williams
Günter Dannoritzer wrote: I modified the vpi_user.c to not needing the other application that comes along with that chapter 2 example and compiled it with: iverilog-vpi pow_vpi.c vpi_user.c iverilog -opow_test.vvp pow_test.v vvp -M. mpow_vpi pow_test.vvp The output I am getting is:

gEDA-user: Re: Icarus Verilog PLI example: PLI_INT32 vs static int

2007-04-02 Thread Stephen Williams
Günter Dannoritzer wrote: Hi, I am trying out some examples from the Sutherland PLI book and for the calltf, compiletf, and sizetf routines the book uses PLI_INT32 type as return type. On the Icarus VPI page http://iverilog.wikia.com/wiki/Using_VPI page in hello.c example I see the use