iverilog/tgt-vvp
Cary R 4dee700ca5 V0.8: Add #! support for MinGW since newer shells support this. 2011-03-15 18:59:29 -07:00
..
Makefile.in V0.8: Fix cleanup and cygwin out of source building 2011-03-14 16:56:03 -07:00
README.txt Spellig fixes. 2005-02-19 16:39:30 +00:00
configure.in V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
draw_mux.c V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
draw_vpi.c V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
eval_expr.c V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
eval_real.c V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
vector.c V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
vvp-s.conf.in Generate VVP_EXECUTABLE flag in conf files. 2003-12-07 19:28:43 +00:00
vvp.c V0.8: Add #! support for MinGW since newer shells support this. 2011-03-15 18:59:29 -07:00
vvp.conf.in Generate VVP_EXECUTABLE flag in conf files. 2003-12-07 19:28:43 +00:00
vvp_config.h.in V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
vvp_priv.h V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
vvp_process.c V0.8: Remove deprecated #ident and fix some other compile warnings 2011-01-12 15:49:03 -08:00
vvp_scope.c Drop trailing spaces 2011-03-04 17:47:59 -08:00

README.txt

THE VVP TARGET

SYMBOL NAME CONVENTIONS

There are some naming conventions that the vvp 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.