Hi Erik: I recall that the intention was to lift the restriction that the maximal property be singly clocked. However, leaving the restriction for this revision of the standard does not seem to be a showstopper as long as there are not contradictory statements or examples. J.H. > X-eda.org-MailScanner-Watermark: 1226508207.47591@U+1nkc3o4dKOokfaS/qhUg > X-Authentication-Warning: server.eda.org: majordom set sender to owner-sv-sc@eda.org using -f > X-eda.org-MailScanner-Watermark: 1226508167.42031@6kVsaPTbmdPdGSkGfV3TyQ > X-ExtLoop1: 1 > X-IronPort-AV: E=Sophos;i="4.33,551,1220252400"; > d="scan'208,217";a="635849926" > From: "Seligman, Erik" <erik.seligman@intel.com> > CC: "sv-ac@server.eda.org" <sv-ac@eda.org>, "sv-sc@eda.org" > <sv-sc@eda.org>, > "stuart@sutherland-hdl.com" > <stuart@sutherland-hdl.com> > Date: Wed, 5 Nov 2008 08:42:17 -0800 > Thread-Topic: Embedding concurrent assertions in procedural code > Thread-Index: Ack/I/3zISk5ZM3gR6GvzJIyIcYMogAPEoNAAAA70tAAAF++UAAAno7Q > Accept-Language: en-US > Content-Language: en-US > X-MS-Has-Attach: > X-MS-TNEF-Correlator: > acceptlanguage: en-US > X-eda.org-MailScanner: Found to be clean, Found to be clean > X-Spam-Status: No, No > Sender: owner-sv-sc@eda.org > X-eda.org-MailScanner-Information: Please contact the ISP for more information > X-MailScanner-ID: mA5GhMaF020624 > X-eda.org-MailScanner-From: owner-sv-sc@server.eda.org > X-OriginalArrivalTime: 05 Nov 2008 16:44:42.0660 (UTC) FILETIME=[CD5F6E40:01C93F65] > > > --_000_D4A21C1D05FCC64D8648615B5082F89B1ACE633Eorsmsx502amrcor_ > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > Hi guys-- > > I went ahead & submitted a proposal to fix this, for now striking just the = > last clause of that paragraph ("and the clocking > event, if specified otherwise, shall be identical to the contextually infer= > red clocking event") and correcting a related example below. > http://www.verilog.org/mantis/view.php?id=3D2516 > > > Dmitry, Lisa, Gord-- please take a look, and if you agree this is the corre= > ct way to go I'll call another vote, and we'll make this a ballot amendmen= > t as well. > > ________________________________ > From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On Beh= > alf Of Seligman, Erik > Sent: Wednesday, November 05, 2008 8:28 AM > To: Korchemny, Dmitry; Lisa Piper > Cc: sv-ac@server.eda.org; sv-sc@eda.org; stuart@sutherland-hdl.com > Subject: [sv-ac] RE: Embedding concurrent assertions in procedural code > > Ugh. This actually contradicts the changes in 2398, which explicitly allow= > such a case: See the example with 'r1'. > > So, I think we need another new proposal to strike the last sentence in the= > paragraph you quote below, to make an issue at balloting. Before I write= > the proposal-- what does "The maximal property of such a concurrent assert= > ion statement shall be singly clocked" mean exactly? Do we still need it, = > or can we strike that part of the sentence too? I thought we were allowing= > multi-clocked properties in general now. > > > > ________________________________ > From: Korchemny, Dmitry > Sent: Wednesday, November 05, 2008 8:21 AM > To: Seligman, Erik; Lisa Piper > Cc: sv-ac@server.eda.org; sv-sc@eda.org; stuart@sutherland-hdl.com > Subject: RE: Embedding concurrent assertions in procedural code > > Hi Erik, > > Are you sure this limitation has been lifted? > > 16.17 Clock resolution reads: > > c) A contextually inferred clocking event from a procedural block supersede= > s a default clocking event. > The contextually inferred clocking event is treated as though it had been w= > ritten as the leading > clocking event of any concurrent assertion statement to which the inferred = > clock applies. The maximal > property of such a concurrent assertion statement shall be singly clocked, = > and the clocking > event, if specified otherwise, shall be identical to the contextually infer= > red clocking event. > > Dmitry > > From: Seligman, Erik > Sent: Wednesday, November 05, 2008 6:11 PM > To: Korchemny, Dmitry; Lisa Piper > Cc: sv-ac@server.eda.org; sv-sc@eda.org; stuart@sutherland-hdl.com > Subject: RE: Embedding concurrent assertions in procedural code > > Actually, r2 is deleted explicitly in 2398 -- see the 8/13 proposal draft, = > p.5, near the top (http://www.verilog.org/mantis/file_download.php?file_id= > =3D3886&type=3Dbug). I think this was because it mentioned a restriction (= > If the clock is explicitly specified with a property, then it shall be iden= > tical to the inferred clock) which is no longer true. > > Stu, can we treat the re-numeration and variable renaming as editorial issu= > es? Would you like me to add a bugnote? > ________________________________ > From: Korchemny, Dmitry > Sent: Wednesday, November 05, 2008 12:54 AM > To: Lisa Piper; Seligman, Erik > Cc: sv-ac@server.eda.org; sv-sc@eda.org; stuart@sutherland-hdl.com > Subject: Embedding concurrent assertions in procedural code > Hi Lisa, Erik, > > It looks to me that the subclause 16.15.6 Embedding concurrent assertions i= > n procedural code is broken. Here are the issues I found: > > * Example with property r2 has been deleted. I could not find the r= > eason either in 1698 or in 2398 > > * If r2 does need to be deleted (though I am not sure it does), the= > numeration of all other properties should be shifted: r3 should become r2,= > etc > > * Examples with r3 and r4 have assignments r1 <=3D reset ? 0 : r1 += > 1; and r1 <=3D reset ? 0 : r2 + 1; which is confusing since r1 and r2 are = > property names in the previous examples. I think they should read: d1 <=3D = > reset ? 0 : d1 + 1; and d1 <=3D reset ? 0 : d2 + 1; > > Could you, please, check? > > Thanks, > Dmitry > > -- > This message has been scanned for viruses and > dangerous content by MailScanner<http://www.mailscanner.info/>, and is > believed to be clean. > > --=20 > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > --_000_D4A21C1D05FCC64D8648615B5082F89B1ACE633Eorsmsx502amrcor_ > Content-Type: text/html; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20 > "urn:schemas-microsoft-com:vml" xmlns:o =3D=20 > "urn:schemas-microsoft-com:office:office" xmlns:w =3D=20 > "urn:schemas-microsoft-com:office:word" xmlns:x =3D=20 > "urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20 > "urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20 > "urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20 > "uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20 > "uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20 > "urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D= > =20 > "urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20 > "urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20 > "urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20 > "urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20 > "urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20 > "http://www.w3.org/TR/REC-html40" xmlns:q =3D=20 > "http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D =3D "DAV:" xmlns:x2 =3D= > =20 > "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =3D=20 > "http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20 > "http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20 > "http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20 > "http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20 > "http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20 > "http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20 > "http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D= > =20 > "http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20 > "http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20 > "http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20 > "http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =3D=20 > "http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =3D=20 > "http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =3D=20 > "http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D= > =20 > "http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20 > "http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t = > =3D=20 > "http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D= > =20 > "http://schemas.microsoft.com/exchange/services/2006/messages" XMLNS:Z =3D= > =20 > "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD> > <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> > <META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]> > <STYLE>v\:* { > BEHAVIOR: url(#default#VML) > } > o\:* { > BEHAVIOR: url(#default#VML) > } > w\:* { > BEHAVIOR: url(#default#VML) > } > .shape { > BEHAVIOR: url(#default#VML) > } > </STYLE> > <![endif]--> > <STYLE>@font-face { > font-family: Calibri; > } > @font-face { > font-family: Tahoma; > } > @font-face { > font-family: Times-Roman; > } > @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; } > P.MsoNormal { > FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif" > } > LI.MsoNormal { > FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif" > } > DIV.MsoNormal { > FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif" > } > A:link { > COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 > } > SPAN.MsoHyperlink { > COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 > } > A:visited { > COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 > } > SPAN.MsoHyperlinkFollowed { > COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 > } > P.MsoListParagraph { > FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-s= > erif"; mso-style-priority: 34 > } > LI.MsoListParagraph { > FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-s= > erif"; mso-style-priority: 34 > } > DIV.MsoListParagraph { > FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-s= > erif"; mso-style-priority: 34 > } > SPAN.EmailStyle18 { > COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe= > rsonal > } > SPAN.EmailStyle19 { > COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso= > nal-reply > } > .MsoChpDefault { > FONT-SIZE: 10pt; mso-style-type: export-only > } > DIV.Section1 { > page: Section1 > } > </STYLE> > <!--[if gte mso 9]><xml> > <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> > </xml><![endif]--><!--[if gte mso 9]><xml> > <o:shapelayout v:ext=3D"edit"> > <o:idmap v:ext=3D"edit" data=3D"1" /> > </o:shapelayout></xml><![endif]--></HEAD> > <BODY lang=3DEN-US vLink=3Dpurple link=3Dblue> > <DIV><SPAN class=3D441194016-05112008><FONT face=3DArial color=3D#0000ff si= > ze=3D2>Hi=20 > guys--</FONT></SPAN></DIV> > <DIV><SPAN class=3D441194016-05112008><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D441194016-05112008><FONT face=3DArial><FONT size=3D2><FO= > NT=20 > color=3D#0000ff>I went ahead & submitted a proposal to fix this, for no= > w=20 > striking just the last clause of that paragraph ("and the=20 > clocking<o:p></o:p></FONT></FONT> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'"><FONT=20 > color=3D#0000ff><FONT face=3DArial>event, if specified otherwise, shall be = > identical=20 > to the contextually inferred clocking event<SPAN class=3D441194016-05112008= > >") and=20 > correcting a related example below.</SPAN></FONT></FONT></SPAN></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'"><FONT=20 > color=3D#0000ff><FONT face=3DArial><SPAN class=3D441194016-05112008><A=20 > href=3D"http://www.verilog.org/mantis/view.php?id=3D2516">http://www.verilo= > g.org/mantis/view.php?id=3D2516</A></SPAN></FONT></FONT></SPAN></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'"><FONT=20 > color=3D#0000ff><FONT face=3DArial><SPAN=20 > class=3D441194016-05112008></SPAN></FONT></FONT></SPAN> </P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'"><SPAN=20 > class=3D441194016-05112008><FONT color=3D#0000ff></FONT></SPAN></SPAN> = > ;</P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'"><SPAN=20 > class=3D441194016-05112008><FONT color=3D#0000ff>Dmitry, Lisa, Gord-- pleas= > e take a=20 > look, and if you agree this is the correct way to go I'll call anothe= > r=20 > vote, and we'll make this a ballot amendment as=20 > well.</FONT></SPAN></SPAN></P></FONT></SPAN></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@server.eda.org=20 > [mailto:owner-sv-ac@server.eda.org] <B>On Behalf Of </B>Seligman,=20 > Erik<BR><B>Sent:</B> Wednesday, November 05, 2008 8:28 AM<BR><B>To:</B>=20 > Korchemny, Dmitry; Lisa Piper<BR><B>Cc:</B> sv-ac@server.eda.org; sv-sc@eda= > .org;=20 > stuart@sutherland-hdl.com<BR><B>Subject:</B> [sv-ac] RE: Embedding concurre= > nt=20 > assertions in procedural code<BR></FONT><BR></DIV> > <DIV></DIV> > <DIV><SPAN class=3D401352216-05112008><FONT face=3DArial color=3D#0000ff=20 > size=3D2>Ugh. This actually contradicts the changes in 2398, which=20 > explicitly allow such a case: See the example with=20 > 'r1'.</FONT></SPAN></DIV> > <DIV><SPAN class=3D401352216-05112008><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D401352216-05112008><FONT face=3DArial color=3D#0000ff si= > ze=3D2>So, I=20 > think we need another new proposal to strike the last sentence in the parag= > raph=20 > you quote below, to make an issue at balloting. Before I write = > the=20 > proposal-- what does "The maximal property of such a concurrent assertion= > =20 > statement shall be singly clocked" mean exactly? Do we still need it,= > or=20 > can we strike that part of the sentence too? I thought we were allowi= > ng=20 > multi-clocked properties in general now.</FONT></SPAN></DIV> > <DIV><SPAN class=3D401352216-05112008><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV> > <DIV><SPAN class=3D401352216-05112008><FONT face=3DArial color=3D#0000ff=20 > size=3D2></FONT></SPAN> </DIV><BR> > <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> > <HR tabIndex=3D-1> > <FONT face=3DTahoma size=3D2><B>From:</B> Korchemny, Dmitry <BR><B>Sent:</B= > >=20 > Wednesday, November 05, 2008 8:21 AM<BR><B>To:</B> Seligman, Erik; Lisa=20 > Piper<BR><B>Cc:</B> sv-ac@server.eda.org; sv-sc@eda.org;=20 > stuart@sutherland-hdl.com<BR><B>Subject:</B> RE: Embedding concurrent asser= > tions=20 > in procedural code<BR></FONT><BR></DIV> > <DIV></DIV> > <DIV class=3DSection1> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Hi Erik,<o:p></o:p></SP= > AN></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SPAN= > ></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Are you sure this limit= > ation has=20 > been lifted?<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SPAN= > ></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">16.17 Clock resolution= > =20 > reads:<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SPAN= > ></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'">c) A=20 > contextually inferred clocking event from a procedural block supersedes a= > =20 > default clocking event.<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'">The conte= > xtually=20 > inferred clocking event is treated as though it had been written as the=20 > leading<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'">clocking = > event=20 > of any concurrent assertion statement to which the inferred clock applies. = > The=20 > maximal<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'">property = > of such=20 > a concurrent assertion statement shall be singly clocked, and the=20 > clocking<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman','serif'">event, if= > =20 > specified otherwise, shall be identical to the contextually inferred clocki= > ng=20 > event.<o:p></o:p></SPAN></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SPAN= > ></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Dmitry<o:p></o:p></SPAN= > ></P> > <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SPAN= > ></P> > <DIV> > <DIV=20 > style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df= > 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium non= > e; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none"> > <P class=3DMsoNormal><B><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN><= > /B><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Seligman, Er= > ik=20 > <BR><B>Sent:</B> Wednesday, November 05, 2008 6:11 PM<BR><B>To:</B> Korchem= > ny,=20 > Dmitry; Lisa Piper<BR><B>Cc:</B> sv-ac@server.eda.org; sv-sc@eda.org;=20 > stuart@sutherland-hdl.com<BR><B>Subject:</B> RE: Embedding concurrent asser= > tions=20 > in procedural code<o:p></o:p></SPAN></P></DIV></DIV> > <P class=3DMsoNormal><o:p> </o:p></P> > <DIV> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">A= > ctually,=20 > r2 is deleted explicitly in 2398 -- see the 8/13 proposal draft, p.5, = > near=20 > the top (</SPAN><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><A=20 > href=3D"http://www.verilog.org/mantis/file_download.php?file_id=3D3886&= > type=3Dbug">http://www.verilog.org/mantis/file_download.php?file_id=3D3886&= > amp;type=3Dbug</A><SPAN=20 > style=3D"COLOR: blue">). I think this was because it mentioned a rest= > riction=20 > (</SPAN></SPAN><SPAN=20 > style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Times-Roman">If the clo= > ck is=20 > explicitly specified with a property, then it shall be identical to the inf= > erred=20 > clock) which is no longer true.</SPAN><SPAN=20 > style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:= > p></SPAN></P></DIV> > <DIV> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:= > p></o:p></SPAN></P></DIV> > <DIV> > <P class=3DMsoNormal><SPAN=20 > style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">S= > tu, can=20 > we treat the re-numeration and variable renaming as editorial issues? = > =20 > Would you like me to add a bugnote?</SPAN><SPAN=20 > style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:= > p></SPAN></P></DIV> > <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><SPAN=20 > style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> > <HR align=3Dcenter width=3D"100%" SIZE=3D2> > </SPAN></DIV> > <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN><= > /B><SPAN=20 > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Korchemny, D= > mitry=20 > <BR><B>Sent:</B> Wednesday, November 05, 2008 12:54 AM<BR><B>To:</B> Lisa P= > iper;=20 > Seligman, Erik<BR><B>Cc:</B> sv-ac@server.eda.org; sv-sc@eda.org;=20 > stuart@sutherland-hdl.com<BR><B>Subject:</B> Embedding concurrent assertion= > s in=20 > procedural code</SPAN><SPAN=20 > style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:= > p></SPAN></P> > <P class=3DMsoNormal>Hi Lisa, Erik,<o:p></o:p></P> > <P class=3DMsoNormal><o:p> </o:p></P> > <P class=3DMsoNormal>It looks to me that the subclause 16.15.6 Embedding=20 > concurrent assertions in procedural code is broken. Here are the issues I= > =20 > found:<o:p></o:p></P> > <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20 > style=3D"FONT-FAMILY: Symbol">·</SPAN><SPAN=20 > style=3D"FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'"> &nbs= > p; =20 > </SPAN>Example with property r2 has been deleted. I could not find the reas= > on=20 > either in 1698 or in 2398<o:p></o:p></P> > <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20 > style=3D"FONT-FAMILY: Symbol">·</SPAN><SPAN=20 > style=3D"FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'"> &nbs= > p; =20 > </SPAN>If r2 does need to be deleted (though I am not sure it does), the=20 > numeration of all other properties should be shifted: r3 should become r2,= > =20 > etc<o:p></o:p></P> > <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20 > style=3D"FONT-FAMILY: Symbol">·</SPAN><SPAN=20 > style=3D"FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'"> &nbs= > p; =20 > </SPAN>Examples with r3 and r4 have assignments r1 <=3D reset ? 0 : r1 += > 1; and=20 > r1 <=3D reset ? 0 : r2 + 1; which is confusing since r1 and r2 are prope= > rty=20 > names in the previous examples. I think they should read: d1 <=3D reset = > ? 0 :=20 > d1 + 1; and d1 <=3D reset ? 0 : d2 + 1;<o:p></o:p></P> > <P class=3DMsoNormal><o:p> </o:p></P> > <P class=3DMsoNormal>Could you, please, check?<o:p></o:p></P> > <P class=3DMsoNormal><o:p> </o:p></P> > <P class=3DMsoNormal>Thanks,<o:p></o:p></P> > <P class=3DMsoNormal>Dmitry<o:p></o:p></P></DIV><BR>-- <BR>This message has= > been=20 > scanned for viruses and <BR>dangerous content by <A=20 > href=3D"http://www.mailscanner.info/"><B>MailScanner</B></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> > > --_000_D4A21C1D05FCC64D8648615B5082F89B1ACE633Eorsmsx502amrcor_-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Nov 5 09:17:09 2008
This archive was generated by hypermail 2.1.8 : Wed Nov 05 2008 - 09:17:24 PST