iverilog/tgt-vvp
Stephen Williams 0b3bc81b76 Remove .cvsignore files.
We are in git now, get rid of this CVS cruft.
2009-01-02 16:06:19 -08:00
..
Makefile.in Revert "Enable -Wshadow by default" 2009-01-01 08:33:26 -08:00
README.txt tgt-vvp generates code that skips nets as inputs. 2001-08-10 00:40:45 +00:00
draw_mux.c Content-free portability fixes. 2008-09-29 18:06:47 -07:00
draw_net_input.c Shadow reduction part 5 2008-12-18 16:42:55 -08:00
draw_switch.c Content-free portability fixes. 2008-09-29 18:06:47 -07:00
draw_ufunc.c Content-free portability fixes. 2008-09-29 18:06:47 -07:00
draw_vpi.c Check that numbers fit into the correct immediate width (32 bits). 2008-10-13 19:56:46 -07:00
eval_bool.c Shadow reduction part 5 2008-12-18 16:42:55 -08:00
eval_expr.c Shadow reduction part 5 2008-12-18 16:42:55 -08:00
eval_real.c Shadow reduction part 5 2008-12-18 16:42:55 -08:00
modpath.c Content-free portability fixes. 2008-09-29 18:06:47 -07:00
vector.c Remove most of the lingering CVS droppings. 2008-12-05 21:48:28 -08:00
vvp-s.conf.in Remove redundant back-end selections. 2008-09-07 16:43:54 -07:00
vvp.c Put a version in the vvp file and have vvp verify compatibility. 2008-11-25 08:01:06 -08:00
vvp.conf.in Remove redundant back-end selections. 2008-09-07 16:43:54 -07:00
vvp_config.h.in Remove most of the lingering CVS droppings. 2008-12-05 21:48:28 -08:00
vvp_priv.h Allow that sum immediate values can be signed. 2008-06-13 13:32:06 -07:00
vvp_process.c Add support for real/realtime arrays. 2008-11-01 20:44:03 -07:00
vvp_scope.c Fix for pr2123173. 2008-12-29 16:09:33 -08: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.