I have a UVM testbench run with questasim. I found something strange with it.
if I run it with -novopt option, the TB will report no error.
if I run it without -novopt option, the TB will report 2 errors indicating some of the behavior is errornous.
I did not fully compare the waveform of the 2 results. I just want to know what is this option doing. does this vopt cause some potential error?
In reply to jie:
the option I used for running is
vsim +define+UVM_NO_DPI -c -do “set SolveArrayResizeMax 0; run -all; q” -l questa.log -f questa.tops -novopt -sv_seed (SEED) +UVM_TESTNAME=(TESTNAME) +UVM_VERBOSITY=FULL
and I used UVM 1.1d
The ‘-novopt’ option is a deprecated feature that was used to prevent design optimization. It is only provided for legacy environments and should never be used unless a Mentor support engineer directs you to use it.
If you are seeing differences between a simulation using -novopt and one that doesn’t, there is most likely a race condition in your environment.
If you need to maintain design visibility, use the ‘+acc’ argument to vopt, or use ‘-voptarguments=+acc’ to vsim. Never use the -novopt option.