iverilog/tgt-vvp
steve 66a579dd67 Handle signed display of unsigned signals. 2005-06-18 15:55:21 +00:00
..
.cvsignore vvp.conf files are generated. 2005-03-18 02:57:23 +00:00
Makefile.in Makefile cleanup. 2004-02-10 19:25:00 +00:00
README.txt tgt-vvp generates code that skips nets as inputs. 2001-08-10 00:40:45 +00:00
configure.in Cleanup and factoring of autoconf. 2004-09-27 22:34:10 +00:00
draw_mux.c Make functors know their own width. 2005-06-17 03:46:52 +00:00
draw_vpi.c Handle signed display of unsigned signals. 2005-06-18 15:55:21 +00:00
eval_expr.c Handle function/task port vectors. 2005-03-12 23:45:33 +00:00
eval_real.c Clean up spurious trailing white space. 2004-10-04 01:10:51 +00:00
vector.c Part selects are done in the compiler, not here. 2005-01-24 05:08:02 +00:00
vvp-s.conf.in Generate VVP_EXECUTABLE flag in conf files. 2003-12-07 19:28:43 +00:00
vvp.c Clean up spurious trailing white space. 2004-10-04 01:10:51 +00:00
vvp.conf.in Generate VVP_EXECUTABLE flag in conf files. 2003-12-07 19:28:43 +00:00
vvp_config.h.in Isolate configure from containing config.h 2004-01-20 21:00:47 +00:00
vvp_priv.h Rework of internals to carry vectors through nexus instead 2004-12-11 02:31:25 +00:00
vvp_process.c Fix bit offsets when processing lval concatenation. 2005-06-15 01:33:33 +00:00
vvp_scope.c Make functors know their own width. 2005-06-17 03:46:52 +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.