Jump to content

Verbosity settings for uvm_report_error/warning/fatal


tudor.timi

Recommended Posts

IMO, the verbosity argument for uvm_report_error/warning/fatal should be deprecated. I know that the general recommendation is to use the macros, but this can still cause problems for people migrating from older OVM versions, where there were no such macros. By just using the migration script "ovm" will be converted to "uvm" and we'd just end up with calls to uvm_report_error(...). This is dangerous because the default value of verbosity for uvm_report_error is UVM_LOW, so running a regression with UVM_NONE will just hide any error messages. As a first step you could make the default verbosity for uvm_report_warning/error UVM_NONE and as a second step remove it completely.

Link to post
Share on other sites

Good suggestions. I would add one more option:

 

1. Enhance the ovm-2-uvm script to convert ovm_report_error/warning to `uvm_error - though it can be little involved at times

 

But changing the default verbosity to NONE seems easy enough.

 

BTW - Adam/Hillel/Thomas - assuming the UVM chairs are hearing these feedbacks, what's the process for fixing/accepting these and notifying the originators of these issues? Some of us are from non-Accellera member companies and hence won't be able to follow your internal discussions. Will there be a formal/informal communication here to summarise the changes? Also any timelines for the same please?

 

Thanks

Srini

Link to post
Share on other sites

Do you think there's any possibility of hosting the UVM repository on a more modern platform?

 

For example, hosting the code on Github rather than Sourceforge would allow contributors to submit patches for review and generally encourage wider participation in the development process.

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...