|
From: Stephen W. <st...@ic...> - 2008-04-29 23:27:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm thinking that it's not a bad time right now to integrate the contributed va_math library into the Icarus Verilog git distribution. We get to decide on a method. 1. The va_math.c code is pretty compact. We could just include it as part of the system.vpi in the vpi/ directory. This would also mean that the va_math.sft becomes part of the system.sft file and every user just gets it. 2. We could include it in the vpi/ directory, but make a separate va_math.vpi module. The vpi/Makefile.in would gain the rules needed to make and install the va_math.vpi module and install the va_math.sft. 3. Create a va_math directory similar to the vpi/ directory. Option #1 has the advantage that it is completely transparent to the Icarus Verilog user, except that now there are all these nifty new system functions. The only disadvantage I can think of it that there is a slight bit of bloat in system.vpi. There is also some name space pollution. Option #2 has the advantage that system.vpi and va_math.vpi are kept lighter weight. Name space pollution is also reduced. The disadvantage is that the user has to use the -mXXX flags to load the va_math library. (That's not unlike the "-lm" flag that C programmers sometimes have to remember.) Option #3 is just a worse version of #2. Preferences? - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIF67orPt1Sc2b3ikRAt0mAJwODv8MHGmVtNeHIdVUBh51n/o5iQCdEijS JLwnW2YMbRILwTMPoP18wPk= =nFy6 -----END PGP SIGNATURE----- |