bbdf622ea5
This patch fixes a number of problems related to the divide and modulus operators. The net version (CA) of modulus did not support a signed version. Division or modulus of a value wider than the machine word did not correctly check for division by zero and return 'bx. Fixed a problem in procedural modulus. The sign of the result is only dependent on the L-value. Division or modulus of a signed value that was the same width as the machine word was creating an incorrect sign mask. Division of a signed value that would fit into a single machine word was not checking for division by zero. Division or modulus of a wide value was always being done as unsigned. Added a negative operator for vvp_vector2_t. This made implementing the signed wide division and modulus easier. |
||
|---|---|---|
| .. | ||
| .cvsignore | ||
| Makefile.in | ||
| README.txt | ||
| configure.in | ||
| draw_mux.c | ||
| draw_net_input.c | ||
| draw_switch.c | ||
| draw_ufunc.c | ||
| draw_vpi.c | ||
| eval_bool.c | ||
| eval_expr.c | ||
| eval_real.c | ||
| modpath.c | ||
| vector.c | ||
| vvp-s.conf.in | ||
| vvp.c | ||
| vvp.conf.in | ||
| vvp_config.h.in | ||
| vvp_priv.h | ||
| vvp_process.c | ||
| vvp_scope.c | ||
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.