Hello Brian, I'm using GHDL with option '--std=93' by default. I also ported the PoC.simulation package to VHDL'08 (it's not @ GitHub yet). The error is the same, just another line, but still the index operation in the NOT table.
Regards
Patrick
-----------------------------------
Wissenschaftliche Hilfskraft
Technische Universität Dresden
Fakultät Informatik
Institut für Technische Informatik
Lehrstuhl VLSI-Entwurfssysteme, Diagnostik und Architektur
01062 Dresden
Tel.: +49 351 463-38451
Fax: +49 351 463-38324
Raum: APB-1020
E-Mail: [email protected]
WWW: http://vlsi-eda.inf.tu-dresden.de
-----Original Message-----
From: Ghdl-discuss [mailto:[email protected]] On Behalf Of Brian
Drummond
Sent: Wednesday, August 12, 2015 11:12 AM
To: [email protected]
Subject: Re: [Ghdl-discuss] Bound check failure in std_logic_1164_body.v93
On Wed, 2015-08-12 at 08:45 +0000, Lehmann, Patrick wrote:
> Hello,
>
>
>
> is a ‘bound check failure’ always related to entity/component binding,
> alternatively
>
> to a mismatch between a component declaration (e.g. in a package) and
> an entity
>
> description?
To any index that isn't within the array bounds, I think.
I absolutely agree that the name of the failing entity would be useful.
> But I think this still does not explain why I get such a failure in
> std_logic_1164_body.v93 …
The function body indexes an array ... presumably the index (a std_logic
value) for this particular call of "not" is garbage. That doesn't tell us why
... as it's .v93 I presume you're not using any of 2008's implicit boolean
operators...
I have seen similar problems in std_logic_1164 when compiling VHDL at higher
optimisation levels (gcc -O2 and above), earlier in the
gcc4.8,4.9 porting process, but those problems got fixed. If you're using
optimisation, perhaps it's worth trying without, to home in on the problem?
-- Brian
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
