dave_59

There have been some improvements to the performance of the field automation macros, but I still do not believe their benefit is worth the cost. You should be able to prove it to yourself by creating a simple testbench with and without the macros.

The reason for the failure is because of the bad constraint. Since the call to randomize is outside of a class declaration, std::randomize() gets called implicitly.

This is just hypothetical, not real SV syntax. I answered this question here: https://verificationacademy.com/forums/coverage/cross-coverage-two-covergroups

You may want to look at the new soft constraint feature of SV1800-2012. A soft constraint is automatically disabled when there is a conflicting constraint. However, then you lose a way of describing your intent. Did you intend to disable the constraint with a new one, or did you add a conflicting constraint by mistake and now you will no longer get an constraint failure.

bhunter, that is incorrect; only case 1 will work. The initialization of automatic variables happens as the scope they declared in come into existance(activated).
 
Each iteration of the for loop creates a new fork/join_none block with a unique value of i.  That unique value of i is used to initialize the local copy of j created for each fork/join_none block. If you put the variable assigment into procedural code of the child threads, the ordering of the execution of those child threads are indetermiate, and at best, deferred until the parent thread blocks or terminates.

I answered this here.

Modules are used for both design and verification. Modules are instantiated to create hierarchy of other modules, interfaces and programs. Programs cannot contain any hierarchy. Just forget about programs.

Please copy the file to the correct location if you install 10.0c and use UVM. With later releases the file should be in the correct place.

The missing files are:
<install>/<uvm_dir>/win32/uvm_dpi.dll
The <uvm_dir> names are: uvm-1.0p1, uvm-1.1 and uvm_reg-1.1.

The files are located at:
<install>/win32/<uvm_dir>/uvm_dpi.dll
Please copy the files to the correct location:
<install>/<uvm_dir>/win32/

From my perspective, I consider the first release of the UVM 1.0p1 a beta release. I strongly suggest you move to 1.1 or later (1.1c was released a month ago).

You don't need the -sv_lib switch when using the UVM package that comes with Questa.