Look into the ncsim log below, the covergroup instances, through are in the same covergoup type, do have their own names. Then why ncsim still output such *N message?
Is there any potential risk, or how can I get rid of such *N messages?
Thanks.
ncsim: *N, COVAUO: (File: AAA.svh, Line: 45):(Time: 879220 NS + 118) Instance coverage of covergroup instance (worklib.dut_pkg::reg_XXX#(int unsigned,4294967295,0,5)::cg8365_1) inside UVM object will be accumulated with instance coverage of other covergroup instances with the same instance name (dut_pkg.reg_XXX#(int unsigned, -1, 0, 5)::cg.reg_Y_set_w_cov_1) and not separately.
ncsim: *N, COVAUO: (File: AAA.svh, Line: 45):(Time: 879220 NS + 118) Instance coverage of covergroup instance (worklib.dut_pkg::reg_XXX#(int unsigned,4294967295,0,5)::cg8327_1) inside UVM object will be accumulated with instance coverage of other covergroup instances with the same instance name (dut_pkg.reg_XXX#(int unsigned, -1, 0, 5)::cg.reg_Y_set_w_cov_2) and not separately.
ncsim: *N, COVAUO: (File: AAA.svh, Line: 45):(Time: 879220 NS + 118) Instance coverage of covergroup instance (worklib.dut_pkg::reg_XXX#(int unsigned,4294967295,0,5)::cg8129_1) inside UVM object will be accumulated with instance coverage of other covergroup instances with the same instance name (dut_pkg.reg_XXX#(int unsigned, -1, 0, 5)::cg.reg_Y_set_w_cov_3) and not separately.