And you all thought we were done... A couple of issues have come up that I thought we had addressed, but I can't seem to find it in the 890 proposal 1. If I have a clockvar output whose target is a variable bit vector, and within a given clock cycle I only drive a part or bit select of that clockvar, do the undriven bits use their previous value? Mantis 890 makes it clear that for a net, an internal variable holds the previous state of the clockvar until a new value is driven, but there is no such wording for driving a target that is a variable. 2. A similar question for unpacked structs and arrays: If a member of an unpacked type is selected in a clockvar drive, then should the entire target variable be assigned with previous values of all the other clockvar members? David Rich Verification Technologist Design Verification & Test Division Mentor Graphics Corporation dave_rich@mentor.com Office: 408 487-7206 Cell: 510 589-2625 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Apr 10 17:41:25 2007
This archive was generated by hypermail 2.1.8 : Tue Apr 10 2007 - 17:41:56 PDT