I think: Actually, 2'b0x + 1 will give you 32'bx. I will give another example. In a casex statement, 2'b0x in a case item expression means that the LSB is don't care. Again, if you give an expression and not just a single number, first the expression is evaluated, and only afterwards is the resulting value interpreted. Shalom From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Irfan Chandurwala Sent: Wednesday, January 16, 2013 07:50 To: sv-ec@eda.org Subject: [sv-ec] Query regarding wildcard arithmetic expressions in wildcard bin definition Hi My query is regarding "what must be correct behavior when arithmetic expression involving wildcard values is part of wildcard bin definition" Ex :: reg [1:0] a ; covergoup cg; coverpoint a { wildcard bins b[] = {2'b0x + 1}; // --> what must be possible bins values ??? } endgroup Ques 1) In the above example what must be the possible bin values in the wildcard bins b1. Options a) 0,1,2,3 b) 0,1 c) Any other possible value Ques 2 ) Which of the below explanation is correct - 1 evaluation of "2'b0x + 1", which is 2'bxx as per LRM section 11.4.3, will be done first and then expansion of wildcard value, which will give us {0,1,2,3} as possible bin values 2 expansion of wildcard value "2'b0x" will be done first and then evaluation of arithmetic expression, which will give us {0,1} as possible bin values 3 Or is there any other behavior for such scenario. Regards, -Irfan -- This message has been scanned for viruses and dangerous content by MailScanner<http://www.mailscanner.info/>, and is believed to be clean. --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jan 17 03:00:10 2013
This archive was generated by hypermail 2.1.8 : Thu Jan 17 2013 - 03:00:25 PST