Here are further tests: ghdl 0.31 on windows: C:\Tools\GHDL\0.31\bin\ghdl.exe: poc-obj93.cf: bad library format
ghdl 0.32 on windows: C:\Tools\GHDL\0.32\bin\ghdl.exe: poc-obj93.cf: bad library format ghdl 0.33dev (hg commit 821) on windows: build_constant: cannot handle IIR_KIND_PHYSICAL_FP_LITERAL (D:\git\SATAController\lib\PoC\tb\misc\misc_Noise_tb.vhdl:17:115) It's independent of '--std=93/02/08'. I moved the code to linux (Debian) with ghdl 0.32rc1 installed: ============================================================================================ ERROR while executing ghdl: /home/paebbels/git/PoC/tb/misc/misc_Noise_tb.vhdl Return Code: 1 -------------------------------------------------------------------------------- build_constant: cannot handle IIR_KIND_PHYSICAL_FP_LITERAL (/home/paebbels/git/PoC/tb/misc/misc_Noise_tb.vhdl:17:115) ******************** GHDL Bug occured **************************** Please report this bug on http://gna.org/projects/ghdl GHDL release: GHDL 0.32rc1 (20141104) [Dunoon edition] Compiled with GNAT Version: 4.9.1 In directory: /home/paebbels/git/PoC/temp/ghdl/ Command line: /opt/gcc-4.9.2/libexec/gcc/x86_64-unknown-linux-gnu/4.9.2/ghdl1 -P. --syn-binding --std=93 --work=test -P./ -P/opt/gcc-4.9.2/lib/gcc/x86_64-unknown-linux-gnu/4.9.2/vhdl/lib//v93/std/ -P/opt/gcc-4.9.2/lib/gcc/x86_64-unknown-linux-gnu/4.9.2/vhdl/lib//v93/ieee/ -quiet -o misc_Noise_tb.s /home/paebbels/git/PoC/tb/misc/misc_Noise_tb.vhdl Exception TYPES.INTERNAL_ERROR raised Exception information: Exception name: TYPES.INTERNAL_ERROR Message: errorout.adb:71 Call stack traceback locations: 0x622a9c 0x6420f0 0x646f3c 0x6cc623 0x6ceb30 0x6bf6fc 0x6b4bb4 0x6ba551 0x6bb4b9 0x6c2595 0x6c0424 0x6c6070 0x6c945e 0x6aedd5 0x6d4b6b 0x6a3c7b 0x6a4d85 0x607897 0x5d934d 0xa7b5c0 0xa7d60e 0x6078e9 0x5d5e45 0x7fb37a53eb43 0x5d666d 0xfffffffffffffffe ****************************************************************** Execution terminated by unhandled exception Exception name: TYPES.INTERNAL_ERROR Message: errorout.adb:71 Call stack traceback locations: 0x622a9c 0x6420f0 0x646f3c 0x6cc623 0x6ceb30 0x6bf6fc 0x6b4bb4 0x6ba551 0x6bb4b9 0x6c2595 0x6c0424 0x6c6070 0x6c945e 0x6aedd5 0x6d4b6b 0x6a3c7b 0x6a4d85 0x607897 0x5d934d 0xa7b5c0 0xa7d60e 0x6078e9 0x5d5e45 0x7fb37a53eb43 0x5d666d 0xfffffffffffffffe /usr/bin/ghdl: compilation error ============================================================================================ 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 David Koontz Sent: Tuesday, June 09, 2015 12:03 AM To: GHDL discuss list Subject: Re: [Ghdl-discuss] Error while handling floating point literals in physical literals On 9/06/2015, at 8:15 am, Tristan Gingold <[email protected]> wrote: > On 08/06/15 21:55, Lehmann, Patrick wrote: >> Hello, >> >> I got an error message that says handling of floating point literals >> in physical literals is not supported. >> >> I can change my code, because it’s just a ‘100.0 MHz’ constant. Is >> this a features that will be implemented >> >> in the future? If I remember correctly, VHDL allows floating point >> literals in physical literal definitions. > > I cannot reproduce the error with the trunk version of ghdl, so I > suppose the issue has already been fixed! It analyzes with ghdl-0.31 on OS X (the gcc version and the mcode version). _______________________________________________ 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
