luke
/
iverilog
mirror of https://github.com/steveicarus/iverilog.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Proof reading.

This commit is contained in:
steve 1999-05-10 00:29:35 +00:00
parent 5de9b7c9f1
commit fcff59f257
1 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.txt
View File

@ -1,12 +1,12 @@
THE ICARUS VERILOG COMPILATION SYSTEM
5/7/99
May 9, 1999
1.0 What is ICARUS Verilog(IVL)?
Icarus Verilog is intended to compile ALL of the Verilog HDL as described
in the IEEE-1364 standard. Of course, it's not quite there yet. I do
handle a mix of structural and behavioral constructs.
in the IEEE-1364 standard. Of course, it's not quite there yet. It does
currently handle a mix of structural and behavioral constructs.
IVL is not aimed at being a simulator in the traditional sense, but a
compiler that generates code employed by back-end tools. These back-
@ -16,8 +16,8 @@ and an XNF (Xilinx Netlist Format) generator. See "vvm.txt" and
2.0 How IVL Works
This tool includes a parser which read in Verilog (plus extensions) and
generates an internal netlist. The netlist is passed to various
This tool includes a parser which reads in Verilog (plus extensions)
and generates an internal netlist. The netlist is passed to various
processing steps that transform the design to more optimal/practical
forms, then passed to a code generator for final output. The
processing steps and the code generator are selected by command line
@ -31,6 +31,10 @@ output of the parse in a list of Module objects in PFORM. The pform
unit. There may be dangling references, and it is not yet clear which
module is the root.
One can see a human readable version of the final PFORM by using the
``-P <path>'' flag to the compiler. This will cause ivl to dump the
PFORM into the file named <path>.
2.2 Elaboration
This phase takes the pform and generates a netlist. The driver selects
@ -40,6 +44,11 @@ netlist.
The elaborate() function performs the elaboration.
One can see a human readable version of the final, elaborated and
optimized netlist by using the ``-N <path>'' flag to the compiler. If
elaboration succeeds, the final netlist (i.e. after optimizations but
before code generation) will be dumped into the file named <path>.
2.3 Optimization
This is actually a collection of processing steps that perform
@ -200,6 +209,9 @@ setenv LD_LIBRARY_PATH /usr/local/lib:$LD_LIBRARY_PATH
ivl -t vvm -o hello.cc hello.vl
g++ hello.cc -o hello -lvvm
(The above presumes that /usr/local/include and /usr/local/lib are
part of the compiler search path, which is usually the case for egcs.)
To run the program
./hello