uvm_object_globals.svh

Summary
uvm_object_globals.svh
Types
uvm_transaction_id_tIntegral type used to represent unique IDs of transactions in <uvm_transaction::set_transaction_id> and <uvm_transaction::get_transaction_id>.
uvm_tr_handle_tIntegral type used to represent transaction handles in <uvm_transaction::get_tr_handle> and associated APIs.
uvm_core_stateImplementation of the uvm_core_state enumeration, as defined in section F.2.10 of 1800.2-2020.

uvm_transaction_id_t

Integral type used to represent unique IDs of transactions in <uvm_transaction::set_transaction_id> and <uvm_transaction::get_transaction_id>.

@uvm-contribFor potential contribution to a future 1800.2 standard.

uvm_tr_handle_t

Integral type used to represent transaction handles in <uvm_transaction::get_tr_handle> and associated APIs.

@uvm-contribFor potential contribution to a future 1800.2 standard.

uvm_core_state

Implementation of the uvm_core_state enumeration, as defined in section F.2.10 of 1800.2-2020.

Note: In addition to the states defined in section F.2.10, this implementation includes the following additional states.

UVM_CORE_PRE_INITThe uvm_init method has been invoked at least once, however the core service has yet to be determined/assigned.  Additional calls to uvm_init while in this state will result in a fatal message being generated, as the library can not determine the correct core service.
UVM_CORE_INITIALIZINGThe uvm_init method has been called at least once, and the core service has been determined.  Once in this state, it is safe to query <uvm_coreservice_t::get>.
UVM_CORE_POST_INITIncluded for consistency, this is equivalent to UVM_CORE_INITIALIZED in 1800.2-2020.

@uvm-contrib Potential contribution to 1800.2

Implementation of uvm_init, as defined in section F.3.1.3 in 1800.2-2020.