Search the Community
Showing results for tags 'uvm_info'.
Found 4 results
Hi all! I've been trying to completely do without the full path of filename when reporting for example instead of UVM_INFO /1/2/3/4/5/6/7/8/filename.sv (linenum) "Message" I want completely remove or shorten the path UVM_INFO /.../filename.sv (linenum) "Message" I've tried using UVM_REPORT_DISABLE_FILE_LINE UVM_REPORT_DISABLE_FILE But it completely removes the filename and line num from the report. I'm looking into the uvm source code and make my own modifications, but I don't want to mess around with the libraries since I share the installation directories. Anybody has done this before? Thank you!
Hi! I need redirect all uvm_info messages to some log file. My testbench contain dut module, some environment modules and classes, which using for monitoring and driving. In environment modules, drivers and monitors exists `uvm_info callings. To save `uvm_info messages to log file In uvm agents build_phase: In console i see messages of two types. 1st type: Messages 1st type outputs by environment modules. Messages 1st type exists in output log. 2nd type Messages 2st type outputs by monitors and drivers. Messages 2st type not exists in log. I need to output to file both type messages .
I've encountered a rather nasty issue with the UVM 1.2 BCL where changing the `uvm_info verbosity from UVM_NONE to UVM_LOW for the same random seed yields different simulation results. Mantis bug logged here: https://accellera.mantishub.com/view.php?id=5482 This is not good practice, BUT - It is possible for the random stability to be affected, for example, if within the `uvm_info macro, a function is called that allocates a new object or randomizes, thus altering the RNG. Example: `uvm_info("SOME_ID", $psprintf("Some number is: %0d", get_some_number()), UVM_LOW) function int get_some_number(); some_object obj = new(); get_some_number = $urandom; endfunction I understand that some effort has been put in to revamping the message reporting mechanism from 1.1 to 1.2, as well as improving the random stability with the insertion of get/set_randstate guards. If this is something that is completely unavoidable in UVM, then it might be a good idea to add this to the UVM User Guide as an example of bad coding.