john_fowler Posted July 7, 2010 Report Share Posted July 7, 2010 Hello all, There is significant concern over the changes to the uvm_objection::raise_objection and uvm_objection::drop_objection. A string argument called 'description' was inserted as the second argument. This 'description' is primarily used when the 'trace_mode' is enabled--not all time. Not only is this a backwards compatibility issue--it allows a silent failure as the simulators will not provide any indication functionality is changing. For instance, in OVM code such as... | ovm_test_done.raise_objection(this, 2); Caused 2 objections to be raised. In UVM, the same code (barring "o to u" change) causes one objection to be raised and a description of '2'. There is no warning, error, etc. generated by the simulators cause this is valid SystemVerilog. I propose that UVM defines the raise/drop_objection APIs with the 'description' argument as the third argument. John Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.