summaryrefslogtreecommitdiff
path: root/cad/verilog
AgeCommit message (Collapse)AuthorFilesLines
2015-11-03Add SHA512 digests for distfiles for cad categoryagc1-1/+2
Problems found with existing distfile for eagle: distfiles/eagle-lin32-7.4.0.run No changes made to eagle/distinfo file. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-02-18Fix race condition.joerg2-3/+12
2014-10-09Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.wiz1-3/+1
2014-06-28Work around build problem seen only in pbulk (remains unclear why).dholland3-3/+37
Disable build dependence on gperf as the build doesn't actually run it, and also for this workaround I need to patch the gperf output file.
2014-02-15Update HOMEPAGE.mef1-2/+2
2014-01-07(Upstream)mef7-24/+119
Icarus Verilog 0.9.7 is Available (August 26th, 2013) ----------------------------- The developers are pleased to announce the next stable release in the 0.9 series, version 0.9.7. Icarus Verilog is a mostly complete implementation of the hardware description language Verilog, as described in IEEE Std 1364-2005. It also includes a number of user requested extensions. It is freely available (open source), is supported on most operating systems, and will be available as a precompiled package for many of these systems. Icarus Verilog 0.9.7 is primarily a bug fix release. Therefore, we recommend people using the 0.9.6 or earlier releases upgrade to 0.9.7 as soon as possible. Version 0.9.7 is the recommended version for all new users. More details, including known limitations, deviation from IEEE Std 1364-2005, where to obtain the source code, and links to some of the precompiled packages can be found in the Release Notes located here: <http://iverilog.wikia.com/wiki/Release_Notes_Icarus_Verilog_0_9_7> (pkgsrc) 0.9.4 to 0.9.7 update and two patches are added for DESTDIR and 'mkdir: dep: Not a directory' problem.
2013-07-18fixes last commitobache1-2/+2
2013-07-17catch up to changes in Makefileobache1-2/+2
(devel/readline/buildlink3.mk => mk/readline.buildlink3.mk)
2013-07-15* .include "../../devel/readline/buildlink3.mk" with USE_GNU_READLINE=yesryoon1-2/+3
are replaced with .include "../../devel/readline/buildlink3.mk", and USE_GNU_READLINE are removed, * .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE are replaced with .include "../../mk/readline.buildlink3.mk".
2012-10-08Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.asau1-2/+1
2012-05-07Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)dholland1-2/+2
It turns out there were a lot of these.
2011-04-13update to 0.9.4drochner6-144/+57
changes: -Language Coverage: -Add support for using the &&, || and ! operators with real constant values -Add support for passing -0.0 from the compiler to the run time -Add support for parsing pull devices that have two strengths specified -Allow multiple attribute instances -bugfixes pkgsrc change: clean up DESTDIR support
2010-02-01DESTDIR supportjoerg4-7/+99
2009-10-08gcc44 fixesdmcmahill2-1/+14
2009-06-14Remove @dirrm entries from PLISTsjoerg1-2/+1
2009-06-11remove an unused patch.obache1-14/+0
2009-05-20Recursive ABI depends update and PKGREVISION bump for readline-6.0 shlibwiz2-2/+4
major change. Reported by Robert Elz in PR 41345.
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-11update to verilog-0.8.7, the latest in the stable 0.8 series.dmcmahill3-42/+41
Release Notes for Icarus Verilog 0.8.7 none (but see below for other releases since the last version in pkgsrc) Release Notes for Icarus Verilog 0.8.6 This is a bug fix update of the 0.8 stable version of Icarus Verilog. The v0.8 series tries to remain as stable as possible while still fixing bugs that are safe to fix. Preprocessor: * Fix parse/preprocess of C-style comments in surpressed ifdef blocks. * Support leading underscore in preprocessor names. Compilation/elaboration issues: * Support min:typ:max expressions in more places. * Fix handling of @* non-input nets. * Do not support system functions in continuous assignments. * Do not support converting vectors to real. * Do not support constant real valued expressions. Run-time ussues: * Fix comparison of negative numbers that happen to be equal. * Fix bad execution of certain expressions caused by code generator bad lookaside handling. * Proper error message for invalid bit selects. * Implement $printtimescale system task. Compiler build issues: * Compile OK evel if libbzip2 is not installed, but do not support LXT2 in that case. Release Notes for Icarus Verilog 0.8.5 This is mostly a bug-fix release for the 0.8 stable branch. * Fix assertions from unary operators with certain operand widths. * Fix incorrect comparison results when in certain cases comparing two signed negative integers. * Latch synthesis has been added to the core synthesizer * Add nand gate support to the edif code generator * Minor compile time errors/warnings * Improved messages from the configure script Release Notes for Icarus Verilog 0.8.4 This is a bug-fix release for the 0.8 stable branch. The 0.8 stable branch updates do not include significant new features (they go into the devel branch instead) nor fixes that are deemed to drastic to include in a stable tool. - Various source code portability problems have been fixed. The 0.8 no longer compiles on many modern systems. - Various bug reports have been put to rest with this release. Some parser errors have been fixed (including a few regressions from 0.8.3) and a few new syntaxes added. - A variety of systhesis bug fixes and enhancements are included in 0.8.4. Currently, synthesis is only actively supported in the 0.8 branch, and the 0.8.4 is the most complete.
2007-08-05Don't use malloc.h.joerg2-1/+16
2006-10-04update to verilog-0.8.3dmcmahill3-16/+17
** Release Notes for Icarus Verilog 0.8.3 This is a new release of the stable 0.8 branch. The changes from 0.8.2 are intended to be evolutionary, rather then revolutionary, to enhance the stability of the branch. Various simulator bugs have been fixed, including (but not limited to): - Detect overrun of timescale vs. precision - Handle more operators in constant expressions - Various ivl crashes and panics fixed. - Some performance bottlenecks have been fixed. - Various tool compilation problems have been fixed. Also, the internal synthesizer (for synthesis targets) has been considerably improved. NOTE that the code generators have not been improved to take advantage of all the changes here, so there is work yet to be done. The mingw build process for compiling in Windows has been reworked. It is now possible (indeed preferable) to compile fully native Icarus Verilog binaries on Windows with no Cygwin tools at all.
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-05-28For building verilog, lex is indeed needed.rillig1-2/+2
2006-05-22Needs bison.joerg1-2/+2
2006-05-21Fixed pkglint warnings. Since bison and lex are not used when building,rillig3-29/+11
they don't need to be defined in USE_TOOLS.
2006-05-06update to verilog-0.8.2. Adds edif output, contains several bug fixes fordmcmahill3-8/+10
compatibility with more c++ compilers.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-2/+2
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-02-10add one...drochner1-0/+39
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-1/+2
2006-01-29add missing USE_LANGUAGESdmcmahill1-1/+3
2005-05-23Removed trailing white-space.rillig1-1/+1
2005-05-22Replace explicit build dependencies on bison and manipulations on thejlam1-7/+5
YACC variable with USE_TOOLS+=bison.
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-02update to verilog-0.8.1. This is a minor bug fix releasedmcmahill2-6/+6
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2004-10-14update to verilog-0.8.dmcmahill6-45/+32
The current release is a considerable improvement over the previous stable release. It includes 20 months of fixes and language coverage improvements. For a complete history of changes, see the release notes for individual snapshots between the 0.7 and 0.8 releases found at ftp://ftp.icarus.com/pub/eda/verilog/snapshots/pre-0.8 A brief list of highlights: - Support for advanced standard data types such as real, - Lots more language support in general, - Kernel of an extensible, interactive debugger is new, - More complete support for user supplied system functions and tasks, including PLI system functions with various return value types, - Better standards compliance for core system tasks and functions in general, including some Verilog 2001 file I/O support, and - Performance improvements in general.
2004-03-22add lex to the GNU_TOOLS list. Needed for SunOS and probably some others.dmcmahill1-2/+2
2004-03-12bl3ifydmcmahill1-7/+4
2004-01-22replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.grant1-2/+2
2004-01-02Fix build with gcc3.jmmv3-1/+28
2004-01-02Require any version of gperf greater than 2.7.2.jmmv1-2/+2
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-05-06Drop trailing whitespace. Ok'ed by wiz.jmmv1-2/+2
2002-12-15update to verilog-0.7dmcmahill3-22/+14
This release represents many bug fixes, expanded language coverage, greatly enhanced xilinx fpga synthesis and several performance enhancements. The complete list is rather long.
2002-02-08update to verilog-0.6dmcmahill3-11/+19
WHAT'S NEW SINCE 0.5? Quite a lot. Innumerable bugs have been fixed, and standards coverage has been improved significantly. Warning and error messages have been improved, and so has compile performance. Gate delays, strength modeling, and floating point delays have all improved since the 0.5 release. If you had trouble with the 0.5 release, the 0.6 release probably fixes your problem. Support for large designs spanning multiple files has been improved dramatically. The usual preprocessor inclusion method still works, but The 0.6 release adds command files for keeping source file lists, and automatic library searches for missing modules. The library mechinisms are compatible with commercial tools, and commercial module libraries can be used with Icarus Verilog. Many compiler limitations related to the size and complexity of large designs have been relaxed or eliminated. There are no known design size limitations remaining in the compiler. Icarus Verilog should be able to handle any design that you have the patience to compile.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-09-27Mechanical changes to 375 files to change dependency patterns of the formjlam1-2/+2
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the packages whose base package name is "foo", and not those named "foo-bar". A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also change dependency examples in Packages.txt to reflect this.
2001-08-04update to verilog-0.5dmcmahill8-111/+33
* The Big Change: VVP Past versions of Icarus Verilog performed simulation by compiling the Verilog design to intermediate C++ code, then in turn compiling that C++ (usually with G++) to a binary executable. This program was then executed to actually run the simulation. The 0.5 compiler, however, uses a custom internal language called "vvp." The vvp code generator writes a program in the vvp language that the vvp interpreter executes. This gets runtime performance similar to the older vvm method, but compile times are much faster. The result of this change is that there is a new program, ``vvp'', that is installed with the existing ``iverilog'' compiler. This program actually executes the simulation generated by the vvp code generator. There are manual pages for the iverilog command and the new vvp command, as well as a QUICK_START document to help you run your first simulation. * What Else Is New The compiler itself is now a lot more robust. While it still does not compile and understand the entire IEEE1364 standard, the compiler is less likely to crash on bad input, gives better error messages, and has generally been cleaned up.