On Fri, 2013-11-29 at 08:27 +1300, David Koontz wrote: > On 29 Nov 2013, at 5:39 am, Adrien Prost-Boucle > <[email protected]> wrote:
> > But with an average of 5kB used per bit, like David mentioned, > > it would not be simple duplication, rather creation of 100 copies of these > > arrays xD > > Not just copies. Also executable code. The question is how big those > something <= (others => '0'); > assignments get unfolded for big arrays. > > Your included file tb.vhd doesn't seem to have anything to do with fsm.vhd > (without seeing component top). > > I had a terrible time with tb.vhd, starting with the editor I was using Again another data point: Editing out both the aggregates and replacing them with (others => (others => '0')), "tb" analyses, elaborates and runs fine - in under a second for each phase. So I see no evidence whatsoever for a problem with initialising these large arrays with (others => (others => '0')); and plenty that the ridiculous line lengths were causing problems; but not necessarily for ghdl. ghdl -a tb.vhd ghdl -e tb tb.vhd:85:8:warning: component instance "top_i" is not bound tb.vhd:13:14:warning: (in default configuration of tb(a)) brian@Gannet:~/Projects/ghdl/play/HLS$ ./tb tb.vhd:126:32:@10ns:(report note): INFO Reset tb.vhd:126:32:@20ns:(report note): INFO Reset tb.vhd:126:32:@30ns:(report note): INFO Reset tb.vhd:130:32:@40ns:(report note): INFO Start tb.vhd:122:32:@500010ns:(report failure): ERROR Too many cycles simulated. Stopping simulation. ./tb:error: report failed ./tb:error: simulation failed On this build, no segfault. - Brian. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
