User guide

21-41
OpenVera Native Testbench
+vera_enable_solver_trace_on_failure
Enables a mode that prints trace information only when the
solver fails to compute a solution, usually due to inconsistent
constraints. Legal values are 0, 1 and 2. When the value of the
option is 2, the analysis narrows down to the smallest set of
inconsistent constraints, thus aiding the debugging process.
+vera_solver_mode
Selects the Vera constraint solver to use. When set to 1, the
solver spends more pre-processing time in analyzing the
constraints, during the first call to randomize() on each class.
Subsequent calls to randomize() on that class are very fast.
When set to 2, the solver does minimal pre-processing, and
analyzes the constraint in each call to randomize().
Class Dependency Based OpenVera Source File
Reordering
In order to ease transitioning of legacy code from Vera’s
make-based single-file compilation scheme to VCS-NTB, where all
source files have to be specified on the command line, VCS provides
a way of instructing the compiler to reorder Vera files in such a way
that class declarations are in topological order (that is, base classes
precede derived classes).
In Vera, where files are compiled one-by-one, and extensive use of
header files is a must, the structure of file inclusions makes it very
likely that the combined source text has class declarations in
topological order.