1800.2-2020-2.0 tackling backward compatibility

[Mark Strickland]

The UVM WG has heard the concerns that backward incompatibility effectively prevents users from migrating to the recent UVM versions, and our response is to eliminate most of the incompatibility in the upcoming release.  So far, we have added back much of the API that was removed.  We still need to test the functionality of this API, but from a compile-time perspective, it is ready to be tried out with customer code.  A snapshot of this developing library can be downloaded from https://accellera.org/images/downloads/drafts-review/UVM_18002-2020-20-pre1tar.gz.  We would like to hear what remaining compile-time problems exist when this version is used instead of 1.1d or 1.2 when compiling user code.  Please post any errors about uvm library contents being "missing".  We will also post patches to address problems that come up.  Your input will really help us make sure that when we deliver the final version of this library, we address all of your backward compatibility concerns.

[dave_59]

Hi Mark,

Looking at this library, It seems that Mantis 3220 has been backed out since UVM 1.2

uvm_report_server.svh:792

    $swrite(time_str, "%0t", $time);

should be

    $swrite(time_str, "%0t", $realtime);
 

-Dave

 

[Mark Strickland]

Thanks for pointing that out Dave.  It looks like it was $realtime in 1.1d and then back to $time in 1.2.  We will change that back to $realtime in the final release of 1800.2-2020-2.0.