iverilog/tgt-vvp
steve 07e49e215e Use the vectorized %assign where appropriate. 2002-11-08 05:00:31 +00:00
..
.cvsignore Add the tgt-vvp code generator target. 2001-03-19 01:20:46 +00:00
Makefile.in Install shared objects as programs, not data. 2002-11-05 02:14:41 +00:00
README.txt tgt-vvp generates code that skips nets as inputs. 2001-08-10 00:40:45 +00:00
configure.in Autoconfig ident support. 2002-08-12 00:27:10 +00:00
draw_mux.c Generate x out for x select on wide muxes. 2002-08-29 03:04:01 +00:00
eval_expr.c Vectorize load from REG variables. 2002-11-07 03:12:17 +00:00
vector.c Add thread expression lookaside map. 2002-09-27 16:33:34 +00:00
vvp.c conditional ident string using autoconfig. 2002-08-12 01:34:58 +00:00
vvp_priv.h Add thread expression lookaside map. 2002-09-27 16:33:34 +00:00
vvp_process.c Use the vectorized %assign where appropriate. 2002-11-08 05:00:31 +00:00
vvp_scope.c draw lpm ff with aset_expr taken into account. 2002-10-23 04:39:35 +00:00

README.txt

THE VVP TARGET

SYMBOL NAME CONVENTIONS

There are some naming conventions that the vp target uses for
generating symbol names.

* wires and regs

Nets and variables are named V_<full-name> where <full-name> is the
full hierarchical name of the signal.

* Logic devices

Logic devices (and, or, buf, bufz, etc.) are named L_<full_name>. In
this case the symbol is attached to a functor that is the output of
the logic device.


GENERAL FUNCTOR WEB STRUCTURE

The net of gates, signals and resolvers is formed from the input
design. The basic structure is wrapped around the nexus, which is
represented by the ivl_nexus_t.

Each nexus represents a resolved value. The input of the nexus is fed
by a single driver. If the nexus in the design has multiple drivers,
the drivers are first fed into a resolver (or a tree of resolvers) to
form a single output that is the nexus.

The nexus, then, feeds its output to the inputs of other gates, or to
the .net objects in the design.