Doubt regarding analysis_export within uvm_tlm_analysis_fifo

Hi ,

I see that the analysis_export within uvm_tlm_analysis_fifo is actually an Imp .

But unlike Imps which terminate the path from port to export , this analysis_export in-turn calls other Imps connected to “put_ap” .

Isn’t this against normal Imps ?

Thanks

In reply to MICRO_91:

Hi ,
I see that the analysis_export within uvm_tlm_analysis_fifo is actually an Imp .
But unlike Imps which terminate the path from port to export , this analysis_export in-turn calls other Imps connected to “put_ap” .
Isn’t this against normal Imps ?
Thanks

A uvm_analysis_imp provides the required write() method implementation to terminate a UVM analysis path. it’s required to override the write() method with an implementation for the uvm_analysis_imp.

uvm_tlm_analysis_fifo don’t have only import. it have ports and imports both. it has two input ports and two output analysis ports.

so uvm_tlm_analysis_fifo terminate the port-export(optional)-imp path using input ports and it start the new path using the output ports(put_ap/get_ap) .