On Wed, Mar 23, 2011 at 05:24:59PM +0100, Sylvere Teissier wrote: > On 23/03/2011 17:15, Lluís Batlle i Rossell wrote: > > GHW files are also a pain in RAM usage by gtkwave. It takes ~2GiB of > > RAM for the > > waves I look at. > > > > Regards, > > Lluís. > > > > An important TODO in grt: > > implement pattern filtering in ghw dumping. > > something like this: > > ./my_design --wave=test.ghw > --dump-only='my_top.my_ip1.*,my_top.my_ip2.my_signal' > > > this will fix the problem of RAM usage, ghw file size and simulation speed
Good, but this may not fix the failures I'm seeing in gtkwave opening the ghw (ghdl 0.29 + gtkwave 3.3.20). And lxt2 can hold all the signals I have just fine in 4MB, while the ghw file is 113MB big. The ram usage of lxt2 is very little in gtkwave, and it works very fast. I still see advantadges in naming the records specially in vcd instead of skipping them in the dump. Regards, Lluís. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
