Veripool

05/23/2014

06:20 PM Verilator Issue #750: Verilator crashes throwing std::bad_alloc exception

Did not re-test yet. But going to close ticket so it does not hang around.

04/24/2014

06:30 PM Verilator Issue #750: Verilator crashes throwing std::bad_alloc exception

I will try to build verilator on my 16G workstation and see how it goes. But I hoped that at least Verilator compiler...

06:06 PM Verilator Issue #750: Verilator crashes throwing std::bad_alloc exception

I think I figure out what file corresponds to "bkk". Here is code around line 144:...

05:30 PM Verilator Issue #750: Verilator crashes throwing std::bad_alloc exception

Do you mean cells.tree? nodep=0x6c6eebf0 is mentioned there but I do not see filename or line number....

05:01 PM Verilator Issue #750: Verilator crashes throwing std::bad_alloc exception

...

04:58 PM Verilator Issue #750 (NoFixNeeded): Verilator crashes throwing std::bad_alloc exception

I am trying to compile a big project with Verilator on 4 cores 4G ram machine. Seems that Verilator slowly eats all a...

03:12 AM Verilator Issue #749 (Closed): Name of instance inside "for" loop clashes with name of an instance located ...

...

04/23/2014

07:26 PM Verilator Issue #659: Support finitely recursive modules

I can trace where check for recursion is made inside GraphAlgRank::vertexIterate, but then it is getting harder to un...

04/22/2014

11:36 PM Verilator Issue #659: Support finitely recursive modules

Is it possible to bump priority of this issue? I failed to use Verilator just because of this _feature_; in a project...

04/21/2014

09:36 PM Verilator Issue #745: always @ ({signal1, signal2, etc}) triggers syntax error, unexpected '{'

forgot to mention that version is 3.856