Thanks John, either way is fine I think, as long as it is stated. Thx. -Bassam. -----Original Message----- From: John Havlicek [mailto:john.havlicek@freescale.com] Sent: Wednesday, July 11, 2007 12:30 PM To: Bassam.Tabbara@synopsys.COM Cc: piper@cadence.com; sv-ac@eda-stds.org Subject: Re: [sv-ac] updated cover sequence proposal Hi Bassam: > 2) The wording of "cover property" being a "one match" is too strong. > There are cases (implication) when more than one match results, in > fact we rely on this (per previous discussion) to define the semantics > of "cover sequence". If there is confusion between using "cover property" with a match item to define the coverage count for "cover sequence", then we can go back to "assert property". In other words, we can say that, for a given attempt of cover sequence (S); the number by which the coverage count is incremented is the same as the number of times "increment_coverage" is executed in the corresponding attempt of assert property (S |-> (1, increment_coverage)); J.H. > X-Authentication-Warning: server.eda-stds.org: majordom set sender to > owner-sv-ac@eda.org using -f > x-mimeole: Produced By Microsoft Exchange V6.5 > Content-class: urn:content-classes:message > Date: Wed, 11 Jul 2007 08:45:19 -0700 > Thread-Topic: [sv-ac] updated cover sequence proposal > Thread-Index: AcfDvetgHwnzAaV0Q9ixHKc1EnDQLwAExp6w > From: "Bassam Tabbara" <Bassam.Tabbara@synopsys.com> > X-OriginalArrivalTime: 11 Jul 2007 15:45:21.0235 (UTC) > FILETIME=[7D13DA30:01C7C3D2] > X-eda.org-MailScanner: Found to be clean, Found to be clean > X-Spam-Status: No, No > Sender: owner-sv-ac@eda.org > X-eda.org-MailScanner-Information: Please contact the ISP for more > information > X-eda.org-MailScanner-From: owner-sv-ac@server.eda.org > > This is a multi-part message in MIME format. > > ------_=_NextPart_001_01C7C3D2.7CD71D29 > Content-Type: text/plain; > charset="US-ASCII" > Content-Transfer-Encoding: quoted-printable > > Hi Lisa, > =20 > 3 comments -- independent issues: > =20 > 1) Do we really need to create a backward incompatibility ? We can > leave cover property (sequence_expr) in and recommend not using or at > least > *deprecate* instead of striking out. It's not an erratum we are > fixing, rather can be thought of as better/clearer syntax + > enhancement to add disable iff -- intended to help users not make things harder short term. > =20 > 2) The wording of "cover property" being a "one match" is too strong. > There are cases (implication) when more than one match results, in > fact we rely on this (per previous discussion) to define the semantics > of "cover sequence". > =20 > 3) Do we need to file a separate proposal for semantics update (the > annex) ? Or are we adding to same ? > =20 > Thx. > -Bassam. > =20 > > ________________________________ > > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of > Lisa Piper > Sent: Wednesday, July 11, 2007 6:18 AM > To: sv-ac@eda-stds.org > Subject: [sv-ac] updated cover sequence proposal > > > > I have uploaded a new version of 1768 - cover sequence. It is > attached for convenience.=20 > > Lisa <<1768_cover_sequence_3.pdf>>=20 > > > --=20 > This message has been scanned for viruses and=20 dangerous content by > MailScanner <http://www.mailscanner.info/> , and is > > believed to be clean.=20 > > --=20 > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > > ------_=_NextPart_001_01C7C3D2.7CD71D29 > Content-Type: text/html; > charset="US-ASCII" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD><TITLE>updated cover sequence proposal</TITLE> <META > http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> > <META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR></HEAD> > <BODY> <DIV><SPAN class=3D740513415-11072007><FONT face=3DArial > color=3D#0000ff si= ze=3D2>Hi=20 Lisa,</FONT></SPAN></DIV> <DIV><SPAN > class=3D740513415-11072007><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D740513415-11072007><FONT face=3DArial > color=3D#0000ff=20 size=3D2>3 comments -- independent > issues:</FONT></SPAN></DIV> <DIV><SPAN > class=3D740513415-11072007><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D740513415-11072007><FONT face=3DArial > color=3D#0000ff si= > ze=3D2>1) Do=20 > we really need to create a backward incompatibility ? We can leave > <EM>cove= r=20 property (sequence_expr)</EM> in and recommend not > using or at least *depre= cate*=20 instead of striking out. It's not > an erratum we are fixing, rather can= be=20 thought of as > better/clearer syntax + enhancement to add disable iff -- int= > ended=20 to help users not make things harder short > term.</FONT></SPAN></DIV> <DIV><SPAN class=3D740513415-11072007><FONT > face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D740513415-11072007><FONT face=3DArial > color=3D#0000ff si= > ze=3D2>2) The=20 > wording of "cover property" being a "one match" is too strong. There > are ca= ses=20 > (implication) when more than one match results, in fact we rely on > this (pe= r=20 previous discussion) to define the semantics of > "cover=20 sequence".</FONT></SPAN></DIV> <DIV><SPAN > class=3D740513415-11072007><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D740513415-11072007><FONT face=3DArial > color=3D#0000ff si= > ze=3D2>3) Do=20 > we need to file a separate proposal for semantics update (the annex) ? > Or a= re we=20 adding to same ?</FONT></SPAN></DIV> <DIV><FONT > face=3DArial color=3D#0000ff size=3D2></FONT> </DIV> <DIV > align=3Dleft><FONT face=3DArial size=3D2>Thx.</FONT></DIV> <DIV > align=3Dleft><FONT face=3DArial size=3D2>-Bassam.</FONT></DIV> > <DIV> </DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Den-us > dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma > size=3D2><B>From:</B> owner-sv-ac@eda.org=20 > [mailto:owner-sv-ac@eda.org] <B>On Behalf Of </B>Lisa > Piper<BR><B>Sent:</B>= =20 Wednesday, July 11, 2007 6:18 > AM<BR><B>To:</B>=20 sv-ac@eda-stds.org<BR><B>Subject:</B> [sv-ac] > updated cover sequence=20 proposal<BR></FONT><BR></DIV> > <DIV></DIV><!-- Converted from text/rtf format --> <P dir=3Dltr><SPAN > lang=3Den-us><FONT face=3DArial>I have uploaded a new ve= rsion of=20 > 1768</FONT></SPAN><SPAN lang=3Den-us> <FONT > face=3DArial>–</FONT></SP= > AN><SPAN=20 > lang=3Den-us><FONT face=3DArial> cover</FONT></SPAN><SPAN > lang=3Den-us> <FO= NT=20 face=3DArial>sequence. It is attached > for convenience.</FONT></SPAN><= SPAN=20 lang=3Den-us> </SPAN></P> <P > dir=3Dltr><SPAN lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN > lang=3Den-us><FONT face=3DArial>Lisa</FONT></SPAN><SPAN= > =20 > lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT > face= =3DArial=20 color=3D#000000 size=3D2> > <<1768_cover_sequence_3.pdf>>=20 > </FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN > lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P > dir=3Dltr><SPAN lang=3Den-us></SPAN></P><BR>-- <BR>This message has > been= scanned=20 for viruses and <BR>dangerous content by <A=20 > href=3D"http://www.mailscanner.info/"></B><B>MailScanner</A>, and is > <BR>be= lieved=20 to be clean. </BODY><br />--=20 <br />This message > has been scanned for viruses and <br />dangerous content by <a > href=3D"http://www.mailscanner.info/"><b>MailScanner</b></a>, and is > <br />believed to be clean. > </HTML> > > ------_=_NextPart_001_01C7C3D2.7CD71D29-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Jul 11 12:37:01 2007
This archive was generated by hypermail 2.1.8 : Wed Jul 11 2007 - 12:37:08 PDT