Hi Ed, Isn't there any scenario where user would not want his assertions in initial block to get executed ever if $assertoff is effective at first clock edge ? Manisha -----Original Message----- From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On Behalf Of Eduard Cerny Sent: Wednesday, August 15, 2007 9:47 PM To: Yaniv.Fais@freescale.com; Eduard Cerny Cc: sv-ac@server.eda-stds.org Subject: [sv-ac] RE: Mantis 1756 Hi Yaniv, this is only useful for concurrent assertions. Immediate assertions are more like "if" statements, in procedural code. it does not affect them in any way. ed > -----Original Message----- > From: Fais Yaniv [mailto:yaniv.fais@freescale.com] > Sent: Wednesday, August 15, 2007 4:28 AM > To: Eduard Cerny > Cc: sv-ac@eda-stds.org > Subject: Mantis 1756 > > > Hi Ed, > > I had an action item to review your proposal regarding > $asserton/off/kill on assertions in initial block and it > seemed fine to > me regarding concurrent assertions. > > These system tasks however influence also immediate assertions - The > proposal seem to refer only to assertions with leading clock > and I was > not sure from the proposal what is the intent regarding immediate > assertions, are they postponed or canceled as in current LRM ? if > postponed then when $asserton is later user are they activated in the > same timepoint ? > > Thanks, > Yaniv > > -- 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 Wed Aug 15 22:06:04 2007
This archive was generated by hypermail 2.1.8 : Wed Aug 15 2007 - 22:06:49 PDT