Mike, I think that 17.5.7 is not clear about what the randomizer should do with A.size and B.size in this example: rand int A[]; rand int B[]; constraint c1 { A.size inside { [1:10] }; } constraint c2 { foreach ( A[ k ] ) B.size == A.size; } constraint c3 { foreach ( B[ k ] ) A.size > 9; } What are the generated values of A.size and B.size? My suggestion is to change the third sentence in the new paragraph of 17.5.7 from: As a result of this implicit ordering between size constraints and iterative constraints, the size method shall be treated as a state variable within the foreach block of the corresponding array. To: All size method calls shall be treated as state variables within all foreach blocks. With this change the randomizer will fail with the example above, but this expected behavior is clear. Bill -----Original Message----- From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Ryan, Ray Sent: Wednesday, November 07, 2007 9:50 PM To: michael.burns@freescale.com; SV_EC List Subject: RE: [sv-ec] New proposal for 2113: Inconsistency in constraining assoc array size Mike, This now looks good. Regards, Ray > -----Original Message----- > From: owner-sv-ec@server.eda.org > [mailto:owner-sv-ec@server.eda.org] On Behalf Of Michael Burns > Sent: Tuesday, October 30, 2007 1:12 PM > To: SV_EC List > Subject: [sv-ec] New proposal for 2113: Inconsistency in constraining > assoc array size > > > Hi folks, > > I've uploaded a new proposal for 2113 - links and notes are below. > Please review and provide feedback. > > Thanks, > Mike > > http://www.eda-stds.org/mantis/view.php?id=2113 > > http://www.eda-stds.org/mantis/file_download.php?file_id=2680&type=bug > > Added new proposal version 2113-D4-20071029.pdf. Changed > 17.5.7 to only remove assoc. arrays and add queues (there is no longer > any description there of resizing queues). Added edits to 17.4 to add > queues and describe how they are resized. > > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Nov 8 07:35:41 2007
This archive was generated by hypermail 2.1.8 : Thu Nov 08 2007 - 07:36:31 PST