Jump to content
Sign in to follow this  
karlzhao

Is this difference betweem UVM1.2 and 1800.2-2017?

Recommended Posts

Dear Sir,

I am reading the spec of 1800.2-2017 these days.

I found some difference betweem UVM1.2 and 1800.2-2017.

For example, the function do_begin_tr has 3 arguments(uvm_transaction tr, string stream_name, integer tr_handle) in the uvm-1.2 source code(/base/uvm_component.svh), but in the section 5.4.2.6 of 1800.2-2017, these is no argument described. Why?

So I have some question:

Is the 1800.2 not just based uvm-1.2?

If a newer version of UVM lib come out, is it compatible with UVM-1.2?

 

I am looking forward to your reply!

Thanks!

 

Karl

Share this post


Link to post
Share on other sites

>Is the 1800.2 not just based uvm-1.2?

1800.2 is based upon uvm12 but there is not a 100% overlap

 

>If a newer version of UVM lib come out, is it compatible with UVM-1.2?

there will be no uvm1.2(a,b,c) aka a newer version matching the uvm12 reference manual. the new version accellera builds will match 1800.2 and eventually support some api from uvm12 due to backward compatibility concerns.

if your env works with uvm12+UVM_NO_DEPRECATED then it should be  small step to 1800.2 

 

/uwe

Share this post


Link to post
Share on other sites

On the specific question of the do_begin_tr() arguments, the source file uvm_component.svh corresponds to section 13.1.6.4 in 1800.2-2017.  Both of those show multiple arguments.  Section 5.4.2.6 corresponds to source file uvm_transaction.svh, and neither of those have arguments.  There should not be a difference in this area.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×