iverilog/tgt-vvp
steve e56b77a43f Add support for wait on list of named events. 2003-12-03 02:46:23 +00:00
..
.cvsignore Ignore autom4te.cache files. 2003-08-10 00:41:26 +00:00
Makefile.in Start the vvp target config files. 2003-11-01 04:22:50 +00:00
README.txt tgt-vvp generates code that skips nets as inputs. 2001-08-10 00:40:45 +00:00
configure.in Use fopen64 to open output file. 2003-05-16 03:22:52 +00:00
draw_mux.c Eliminate use of ivl_lpm_name function. 2003-02-25 03:40:45 +00:00
draw_vpi.c Fix word register leak. 2003-04-23 02:22:47 +00:00
eval_expr.c Slightly more efficient unary minus. 2003-10-01 17:44:20 +00:00
eval_real.c Add % in real expressions. 2003-05-25 02:50:08 +00:00
vector.c Wider thread vector limit. 2003-07-03 17:44:10 +00:00
vvp-s.conf Move the DLL= flag to target config files. 2003-11-13 05:55:33 +00:00
vvp.c Use fopen64 to open output file. 2003-05-16 03:22:52 +00:00
vvp.conf Move the DLL= flag to target config files. 2003-11-13 05:55:33 +00:00
vvp_priv.h Remove short int restrictions from vvp opcodes. 2003-06-17 19:17:42 +00:00
vvp_process.c Add support for wait on list of named events. 2003-12-03 02:46:23 +00:00
vvp_scope.c Emit .event inputs before the .event statement. 2003-10-09 23:45:03 +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.