Hello,

I need a couple of details concerning the exact working
of GHDL :

  * During syntax analysis, it seems that many errors lead
    to a "dirty exit" of the Ada runtime library, such as


bash-4.0$ ghdl -s alarme.vhd
alarme.vhd:11:92: extra ';' at end of interface list
alarme.vhd:21:11: identifier expected here

******************** GHDL Bug occured ****************************
Please report this bug on http://gna.org/projects/ghdl
GHDL release: GHDL 0.29dev (20090921) [Sokcho edition]
Compiled with GNAT Version: 4.4.2 20091222 (Red Hat 4.4.2-20
In directory: /media/disk/fpga/montre_sources/
Command line:
ghdl -s alarme.vhd
Exception STORAGE_ERROR raised
Exception information:
Exception name: STORAGE_ERROR
Message: stack overflow (or erroneous memory access)
Call stack traceback locations:
0x80fedcb
******************************************************************

Is this normal ? Or is GHDL lazily coded and relying on
ADA's bound checks to reduce the code size and coding time ?


   * I read in the "info" manual that :

    For the elaboration command, `GHDL' re-analyzes all the
configurations, entities, architectures and package declarations, and
creates the default configurations and the default binding indications
according to the LRM rules.

   If there is already a previous analysis with ghdl -a,
then why re-analyzing ? Can we skip ghdl -a then ?
I don't see the point of this behaviour ...


Thanks for your answers,
yg
-- 
http://ygdes.com / http://yasep.org


_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to