iverilog/tgt-vvp
steve 76a77fdd36 Printed nexus names need not use ivl_nexus_name. 2003-03-03 23:05:49 +00:00
..
.cvsignore Add the tgt-vvp code generator target. 2001-03-19 01:20:46 +00:00
Makefile.in Merge vpi_call and vpi_func draw functions. 2003-02-28 20:21:13 +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 Eliminate use of ivl_lpm_name function. 2003-02-25 03:40:45 +00:00
draw_vpi.c Merge vpi_call and vpi_func draw functions. 2003-02-28 20:21:13 +00:00
eval_expr.c Merge vpi_call and vpi_func draw functions. 2003-02-28 20:21:13 +00:00
eval_real.c Handle real value subtract and comparisons. 2003-02-07 02:46:16 +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 Merge vpi_call and vpi_func draw functions. 2003-02-28 20:21:13 +00:00
vvp_process.c Merge vpi_call and vpi_func draw functions. 2003-02-28 20:21:13 +00:00
vvp_scope.c Printed nexus names need not use ivl_nexus_name. 2003-03-03 23:05:49 +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.