Hi Roberto,
I don't know if that helps, but I was running into these kind of crashes
when accidentally connecting a signal to an entity or other similar
cases where I'd slap my own forehead HARD.
ghdl should be pretty good at boundary checks, but can go haywire when
doing unexpected and "forbidden" things..
Also, it helps to track down errors (even without knowing much about
ghdl internals) when running the simulation from inside gdb and checking
the stack backtrace ('bt'). I think this technique is mentioned
somewhere in the GHDL docs.
Good luck,
- Martin
> I have been trying hard to get rid of the error message
> "bound check failed (#9)" without any success, so here
> goes the request for help:
>
> below is the code for an ALU, based on Hennessy&Patterson's MIPS.
>
> simulation breaks, SOMETIMES, at the LUI clause of the case.
> All other clauses passed several tests. The ASSERT at the
> bottom prints the results correctly. Further down is the code
> where the ALU instance is embedded.
>
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
