Hi Thanks for your reply. I needed some more clarification regarding binsof such as 1) what is the driving factor for including cross bins that are not defined by user. For example , in below shown cross x1, bins <i[1],j[0]> and <i[1],j[1]> are also included although user have not specified them. 2) why cross bins specified by binsof are only scalar bins. Regards, Abhishek David Scott wrote: > Yes, I believe you are correct. This was clarified in Mantis 1655, > which did not make it into 2008 Draft 3a. I believe 1655 has had all > changes necessary for Champions approval, though it has not yet been > finally approved. (It was approved by SV-EC but rejected by the > Champions with friendly amendments suggested.) > > http://eda.org/svdb/view.php?id=1655 > > -- David Scott, Mentor Graphics > > > Abhishek Tiwari wrote: > >> **Hello All, >> >> I have below interpretation regarding semantics >> of "binsof" construct in functional coverage.Please >> let me know if I am correct. >> >> >> *int* i,j; >> *covergroup* ct; >> *coverpoint* i { *bins* i[] = { [0:1] }; } >> *coverpoint* j { *bins* j[] = { [0:1] }; } >> x1: *cross* i,j { >> *bins* i_zero = *binsof*(i) *intersect* { 0 }; >> } >> *endgroup* >> >> ** >> *cross* x1 has the following three bins: >> >> i_zero >> <i[1],j[0]> >> <i[1],j[1]> >> >> Now, suppose at simulation time >> below two values of <i, j> were sampled >> <0, 0> >> <1, 0> >> >> Then only two bins, namely i_zero and <i[1], j[0]> >> will be covered and bin <i[1], j[0]> will be uncovered. >> Hence coverage of cross x1 will be 2/3 . >> >> >> Regards, >> Abhishek >> >> >> >> >> >> >> >> >> >> > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Sep 20 03:44:50 2007
This archive was generated by hypermail 2.1.8 : Thu Sep 20 2007 - 03:45:24 PDT