> Tristan wrote: > > > >> FWIW, if I force an Integer-Out-of-Range error ( as opposed to an > >> Index-Out-of-Range error ), I get the desired results: > >> c:\ghdl\ghdl-0.31-patched\bin\ghdl.exe:error: bound check failure > at integer_range_test.vhd:15 > >> c:\ghdl\ghdl-0.31-patched\bin\ghdl.exe:error: simulation failed > > > > Yes, but an out of range integer is handled like an out of range > index. > > > > Overflows are triggered when a result is not representable, e.g.: > integer'high + 1 > > > To clarify: > > The original issue[1] that I found with regards to bug16782 was a > missing bound check message, and abnormal program exit, when Windows > ghdl-mcode encounters an **index** out of range.
Ah Ok. Indeed, I missed that. Have you checked wether this has been fixed in the trunk ? (I'd like to know wether this is a new bug or simply a bug in 0.31) Tristan. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
