Description of problem: Upstream claims with the 0.28 release that they support VHDL standard 2008. http://ghdl.free.fr/NEWS However it doesn't seem the case on the fedora ghdl package. Can you please enable it ? Version-Release number of selected component (if applicable): ghdl-0.28-0.130svn.0.fc12.i686 How reproducible: everytime Steps to Reproduce: 1. Analyse any vhdl design with --std=08 2. 3. Actual results: chitlesh(vhd08test)[1]$ ghdl -a --std=08 generic_tb.vhd /usr/libexec/gcc/i686-fedora_ghdl-linux/4.3.4/ghdl1:*command-line*: cannot find "std" library generic_tb.vhd:0: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. ghdl: exec error ******************** 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 20091027 (Red Hat 4.4.2-7) In directory: /home/chitlesh/vhd08test/ Command line: ghdl -a --std=08 generic_tb.vhd Exception STORAGE_ERROR raised Exception information: Exception name: STORAGE_ERROR Message: stack overflow (or erroneous memory access) Call stack traceback locations: 0x80fedbb ****************************************************************** Expected results: Should support the VHDL standard 2008 Additional info: FYI I've setup a wiki page https://fedorahosted.org/fedora-electronic-lab/wiki/Digital/ghdl to detail the features fedora ghdl support. I would appreciate if you can help us write anything useful for fedora users. Thank you.
Looks like an upstream (as opposed to fedora packaging) problem. The makefile only contains partial instructions to build the v08 libraries. I will ask upstream why that is the case. Does your testbench need anything v08 specific? Could you attach it to this bugreport?
I've created the testbench to verify the vhdl std 2008 features. The two most important changes to this stages included in the attached testbench: 1. The use of "all" in the sensitivity list >>> dff : process (all) is 2. New condition operator ?? >>> if ?? reset then
Created attachment 374618 [details] simple test case of the vhdl 2008 std
Hello thomas, Can you please create a scratch build of the latest devel snapshot please ? I'll try to test those 2008 standards. At the same time, I would like to debug the (verilog -> vhdl) translation with iverilog. In accordance to this post, it seems that our ghdl package might entailed some bugs. http://sourceforge.net/mailarchive/forum.php?thread_name=4B2415D5.20907%40nickg.me.uk&forum_name=iverilog-devel thanks, Chitlesh
Chitlesh, the latest devel snapshot is AFAIK svn131, which is already built for F10, F11, F12 and rawhide. 2008 is only minimally functional, however. You will not have the ieee libraries, as they apparently don't compile in 2008 mode. I have sent a mail detailing the problem to Tristan, so at the moment there's probably little benefit in testing 2008. At least the ldelay5.vhd problem looks to me like a bug in the vhdl source code, even a commercial compiler bails out (the case statement must cover all cases!) Thomas
thanks for the quick response. I'm having timeouts with koji, might be due to the scheduled outage. I'm free on monday (the whole day). Please feel free to ask me to test something for ghdl.
About comment #4 (iverilog testsuite : translate verilog to vhdl): There was indeed a bug with ghdl. Upstream just close my bug report. http://gna.org/support/?2463
Ah ok I did not see your upstream bug report. Yes, upstream fixed it because I debugged the problem and sent a patch 8-) But back to the original subject of this bug report: 2008 is only very basically working, it does not even work well enough to compile the ieee libraries. So don't hold your breath about 2008 being usable anytime soon.
Ok, then let's close this bug. Could you send a mail to FEL's mailing list to let us know when 2008 is good enough to test it?
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping