• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. How to disable automatically-generated cross bins?

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 17701
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to disable automatically-generated cross bins?

archive
archive over 11 years ago

 Consider the following example code:(it's an example in SystemVerilog P1800-2009, Page 500)

int i,j;
covergroup ct;
coverpoint i { bins i[] = { [0:1] }; }
coverpoint j { bins j[] = { [0:1] }; }
x1: cross i,j;
x2: cross i,j {
bins i_zero = binsof(i) intersect { 0 };
}
endgroup

Cross x2 has the following bins:
i_zero // user-specified bin for
(i[1],j[0]) // an automatically-generated bin that is retained
(i[1],j[1]) // an automatically-generated bin that is retained

My question is: if I only want the first bin, i.e. i_zero, what should I do? I don't want automatically-generated cross bins, I just want user-defined bins, is there some method to disable "automatically-generated cross bins"?

Thanks a lot!

  • Cancel
Parents
  • muffi
    muffi over 11 years ago

    We have provided support for a new option "option.cross_auto_bin_max" for crosses in 12.10 -s13 release.

    The cross_auto_bin_max option is defined at the covergroup level. So, the value of cross_auto_bin_max at covergoup level will propagate to cross level and total number of cross autobins will be 0. This option takes '0' as the only possible value else an error will be reported by the tool.

    If option.cross_auto_bin_max=0 is specified in a cross definition then none of the cross autobins will be saved in the database and will not be reported as well.

    Hope this helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • muffi
    muffi over 11 years ago

    We have provided support for a new option "option.cross_auto_bin_max" for crosses in 12.10 -s13 release.

    The cross_auto_bin_max option is defined at the covergroup level. So, the value of cross_auto_bin_max at covergoup level will propagate to cross level and total number of cross autobins will be 0. This option takes '0' as the only possible value else an error will be reported by the tool.

    If option.cross_auto_bin_max=0 is specified in a cross definition then none of the cross autobins will be saved in the database and will not be reported as well.

    Hope this helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information