On 27 May 2013, at 10:04 AM, Svenn Are Bjerkem <svenn.bjer...@googlemail.com> wrote:
> Sometimes it is better to move the troubled kid out of the community. Having > a clean-room version of the gcc version compatible with ghdl in a location > where apt-get cannot touch it seems very much a way around the current > problem. Problem for me as a GHDL user is that building gcc in /usr/local or > /opt/local and then build GHDL on top of that needs a teaspoon step-by-step > instruction or a script. So far I am stopping any update or install on my > Debian which would remove GHDL. That also means I am stuck at whatever GHDL > version available in Debian/sid. I would really like to use OSVVM, but my > lack of gcc-fu prevents me from that. > There's Peter Gavin's ghdl PPA as a model, this one for ubuntu 12.04 and 12.10: https://launchpad.net/~pgavin/+archive/ghdl Mind, it takes a leap of faith to trust someones Personal Package Archive. I've recently used this one to load ghdl on a lubuntu 12.10 virtual machine. By selecting 'view package details' and expanding the packages you can access the contents for download and manual install. It installed in /usr/lib/ghdl with a shell script in /usr/bin to invoke ghdl. The sizes imply the 12.04 and 12.10 versions may be identical. Someone added a 13.04 build while I was writing this up. How do I create a PPA? And it does appear it takes someone willing to bell the cat with Brian Drummond's OSVVM updates and the latest svn release (r150). I've compiled both into an OS X mcode version but don't a) have anyway to upload to free.fr and b) don't currently have an environment to link to 10.6/10.5 runtime libraries (just 10.8/10.7). I've done a Linux mcode version sometime in the last year just to prove you could. It should be possible to do one with the changes easily enough. The mcode version is only i386, currently doesn't have x86_64 mappings for some IR constructs needing x86_64 equivalents for non-supported instructions. We've seen from what René Doß has done recently with foreign functions it's very desirable to keep the gcc version going. I haven't built gcc versions recently. From Brian Davis and others we see the Windows mcode version could use updating as well. I have no capacity to deal with Windows versions of ghdl whatsoever. As a community we don't have access to any release validation mechanism used by Tristan prior to releases (and we've seen Windows version problems in any event). You can easily separate issues into gcc and VHDL. I downloaded a copy of VESTs from Clifton Labs in 2006, and while the tests do have some errors that could use some fixes they are a superset of the last VHDL validation suite and also released under GPLv2. The tests aren't available anymore on the web, they were found only on ftp sites and I'd like to find a home for them. You can imagine they are the basis for various vendor's test suites. The test suite is intended to be run using dejagnu, has an out of date and not-applicable-to-ghdl test harness, and either using it or doing something reminiscent of the last vhdl validation suite using scripts might be in order. VESTs is intended to be extensible for those test cases you use to demonstrated reported problems and demonstrate fixes. Test case coverage (depending on who you ask) is somewhere around 46 percent for 1076-1993. I'd offer to screen any failures the first time playing VHDL lawyer and fix any broken test cases that could be fixed. It can take hours to screen each one, hopefully I'm not biting off more than I can chew. In general you need to check the LRMs for all supported 1076 releases.
_______________________________________________ Ghdl-discuss mailing list Ghdl-discuss@gna.org https://mail.gna.org/listinfo/ghdl-discuss
