From: Cary R. <cy...@ya...> - 2008-03-15 19:02:35
|
--- Stephen Williams <st...@ic...> wrote: > > iverilog -c t2.inpfile -s cpu takes ~30min and needs 8.5Gb, > > a.out takes 6 min and 4.5GB. > > Thanks for these results. Yeah, the performance issues kinda sting > when I'm reminded, so we need to gradually start giving them more > attention. As Icarus Verilog gets ever more complete and bug free, > people throw ever larger designs at it. In some cases, the limiting > factor for adoption is no longer its completeness but its performance:-O That must not be much of a runtime test! The runtime has always been the slowest part for me. I have ideas on how to improve both the compilation and runtime performance. It's just finding enough time to working on them. The problem lately, and it's mostly a good one, is that the more improvements we do the more bug reports we seem to be getting. I try to fix the easy ones as they come in, but like Steve said we could really use a couple more core developers. If anyone is interested and has some spare time I have a bunch of changes that I would like to do to the system functions (vpi directory) that are not very hard. Most of it is better error messages using the new file and line information along with some better argument checking. I have been saving this as an easy task to do once I'm done, note I didn't say finished, with the expression code. I'm willing to provide guidance on what I think needs to be done if anyone is interested. Cary ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |