iverilog

History

steve 89314d4772 Do not use hierarchical names of memories to generate vvp labels. -tdll target does not used hierarchical name string to look up the memory objects in the design.		2002-08-04 18:28:14 +00:00
..
.cvsignore	Add the tgt-vvp code generator target.	2001-03-19 01:20:46 +00:00
Makefile.in	Generate code for wide muxes.	2002-07-08 04:04:07 +00:00
README.txt	tgt-vvp generates code that skips nets as inputs.	2001-08-10 00:40:45 +00:00
configure.in	Support compile on MacosX 10.1.1 (Timothy J. Wood)	2001-11-17 17:57:58 +00:00
draw_mux.c	Fix check for select size.	2002-07-16 03:15:11 +00:00
eval_expr.c	Do not use hierarchical names of memories to	2002-08-04 18:28:14 +00:00
vvp.c	Support multiple root modules (Philip Blundell)	2001-10-19 21:53:24 +00:00
vvp_priv.h	Do not use hierarchical names of memories to	2002-08-04 18:28:14 +00:00
vvp_process.c	Do not use hierarchical names of memories to	2002-08-04 18:28:14 +00:00
vvp_scope.c	Do not use hierarchical names of memories to	2002-08-04 18:28:14 +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.