Hi Manisha: I also think that it is important to have default disable apply to nested declarations. This technical point was discussed in the committee before and we decided that the default disable should descend into a nested declaration unless the nested declaration itself has a default disable. J.H. > X-Authentication-Warning: server.eda.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: Tue, 20 Nov 2007 09:44:07 -0800 > X-MS-Has-Attach: > X-MS-TNEF-Correlator: > Thread-Topic: [sv-ac] 1648 - default disable iff > Thread-Index: AcgmZT61XiaUhw19R6+O6jlORPUxVgAmgLUgABGTJ2AAEti/IAEClDew > From: "Kulshrestha, Manisha" <Manisha_Kulshrestha@mentor.com> > X-OriginalArrivalTime: 20 Nov 2007 17:44:10.0126 (UTC) FILETIME=[F4C14AE0:01C82B9C] > 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_01C82B9C.F4718EBF > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > Hi Lisa, > > =20 > > I guess it is important to have default disable iff apply to nested > modules also. Probably you can add some extra language to make that > clear along with your current suggestions.=20 > > =20 > > What do others think ? > > =20 > > Manisha > > =20 > > From: Lisa Piper [mailto:piper@cadence.com]=20 > Sent: Friday, November 16, 2007 1:11 AM > To: Kulshrestha, Manisha; sv-ac@eda.org > Subject: RE: [sv-ac] 1648 - default disable iff > > =20 > > Thanks for reviewing this so promptly! I have some comments and > questions below.=20 > > =20 > > ________________________________ > > From: Kulshrestha, Manisha [mailto:Manisha_Kulshrestha@mentor.com]=20 > Sent: Thursday, November 15, 2007 12:36 AM > To: Lisa Piper; john.havlicek@freescale.com; sv-ac@eda.org > Subject: RE: [sv-ac] 1648 - default disable iff > > =20 > > Hi, > > =20 > > With the change in the name of default disable, I would like the title > of 16.15 to reflect that change i.e. change the title to 'Default > disable iff resolution'. > > [Lisa Piper >>>] done > > =20 > > I do not think that section 22.8 has any information about how default > disable iff should be resolved. It only deals with variable, task, > function, named block and generate blocks. So, how do we treat default > disable iff : like a variable declaration or a task declaration ? I > think it is better to have scoping information in this section itself as > default disable iff does not behave like any of the above. > > =20 > > There is another statement "It provides a default disable condition to > all concurrent assertions in the scope of the default disable iff > declaration, > > in accordance with the scope rules of 22.8.". I am not sure which > scoping rules are we referring to from 22.8 ? > > [Lisa Piper >>>] I was mostly referring to: "If an identifier is > referenced directly (without a hierarchical path) within a task, > function, named block, or > > generate block, it shall be declared either within the task, function, > named block, or generate block locally or > > within a module, interface, program, task, function, named block, or > generate block that is higher in the > > same branch of the name tree that contains the task, function, named > block, or generate block. If it is > > declared locally, then the local item shall be used; if not, the search > shall continue upward until an item by > > that name is found or until a module, interface, or program boundary is > encountered. If the item is a variable, > > it shall stop at a module boundary; if the item is a task, function, > named block, or generate block, it continues > > to search higher level modules until found. This fact means that tasks > and functions can use and modify the > > variables within the containing module by name, without going through > their formal arguments." > > =20 > > I was picturing that you can declare a new "Default disable iff" in any > scope were a re-declaration is allowed, like a variable, and then this > applies. I guess with the BNF as it is, this is not true - it cannot be > defined in a named block or task or function. > > =20 > > In the proposal it says: "Declaring more than one default disable iff > item within the same module, interface, or program shall be an error." . > This statement does not fit with the new scheme of allowing default > disable iff in generate blocks. Because effectively there may be > multiple declarations inside same module but they may be in generate > block in the module.=20 > > [Lisa Piper >>>]. I can still re-use most of the wording from 22.8:=20 > > =20 > > Default disable iff shall be declared either within a the task, > function, named block, or generate block locally or > > within a module, interface, program, task, function, named block, or > generate block that is higher in the > > same branch of the name tree that contains it. the task, function, named > block, or generate block. If it is > > declared locally, then the local item shall be used; if not, the search > shall continue upward until an item by > > that name is found or until a module, interface, or program boundary is > encountered. (so nested modules would not be able to adopt the default > disable of the top module - is this ok? Should a default disable iff > also apply to instances contained in the module - I thought not since > signals must be ports. )=20=20 > > More than one default disable iff item within the same scope is an > error.=20 > > =20 > > I thought of another interesting question. If I define my default > disable iff at my top level module to be a signal called reset, and then > I have a generate block within that defines its own reset signal but > does not re-define the default disable iff, then which reset signal is > used? I would assume it is the reset in the scope of the default > disable iff definition. Do you agree? > > =20 > > I think referring to module, interface and program everywhere in this > paragraph is not right as default disable iff can be inside generates > also.=20 > > =20 > > =20 > > Thanks. > > Manisha > > From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On > Behalf Of Lisa Piper > Sent: Thursday, November 15, 2007 2:51 AM > To: john.havlicek@freescale.com; sv-ac@server.eda.org > Subject: [sv-ac] 1648 - default disable iff > > =20 > > The change was pretty simple as it turns out. > > =20 > > A default disable iff may be declared as an item within a module, > interface, or program. It provides a default disable condition to all > concurrent assertions in the scope of the default disable iff > declaration, in accordance with the scope rules of 22.8. > > =20 > > I made one other change. The label and section number for 16.48 was > wrong. It was a duplicate of the previous. > > =20 > > I did not make any other changes. I have uploaded it to Mantis. > > =20 > > Lisa > > =20 > > -----Original Message----- > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of John > Havlicek > Sent: Tuesday, November 13, 2007 9:22 PM > To: sv-ac@eda.org > Subject: [sv-ac] notes from SV-AC meeting 2007-11-13 > > =20 > > Hi Folks: > > =20 > > My notes from today's meeting are attached. > > =20 > > Please let me know if changes are required. > > =20 > > J.H. > > =20 > > --=20 > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > =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_01C82B9C.F4718EBF > Content-Type: text/html; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= > osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = > xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema= > s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html= > 40"> > > <head> > <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> > <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> > <!--[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 Definitions */ > @font-face > {font-family:Courier; > panose-1:2 7 4 9 2 2 5 2 4 4;} > @font-face > {font-family:Mangal; > panose-1:0 0 4 0 0 0 0 0 0 0;} > @font-face > {font-family:Mangal; > panose-1:0 0 4 0 0 0 0 0 0 0;} > @font-face > {font-family:Calibri; > panose-1:2 15 5 2 2 2 4 3 2 4;} > @font-face > {font-family:Tahoma; > panose-1:2 11 6 4 3 5 4 4 2 4;} > @font-face > {font-family:Consolas; > panose-1:2 11 6 9 2 2 4 3 2 4;} > /* Style Definitions */ > p.MsoNormal, li.MsoNormal, div.MsoNormal > {margin:0in; > margin-bottom:.0001pt; > font-size:12.0pt; > font-family:"Times New Roman","serif";} > a:link, span.MsoHyperlink > {mso-style-priority:99; > color:blue; > text-decoration:underline;} > a:visited, span.MsoHyperlinkFollowed > {mso-style-priority:99; > color:purple; > text-decoration:underline;} > p.MsoPlainText, li.MsoPlainText, div.MsoPlainText > {mso-style-priority:99; > mso-style-link:"Plain Text Char"; > margin:0in; > margin-bottom:.0001pt; > font-size:12.0pt; > font-family:"Courier New";} > span.PlainTextChar > {mso-style-name:"Plain Text Char"; > mso-style-priority:99; > mso-style-link:"Plain Text"; > font-family:Consolas;} > span.plaintextchar0 > {mso-style-name:plaintextchar; > mso-style-priority:99; > font-family:Consolas;} > span.EmailStyle20 > {mso-style-type:personal; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.EmailStyle21 > {mso-style-type:personal; > font-family:"Arial","sans-serif"; > color:blue; > font-weight:normal; > font-style:normal; > text-decoration:none none;} > span.EmailStyle22 > {mso-style-type:personal-reply; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > .MsoChpDefault > {mso-style-type:export-only; > font-size:10.0pt;} > @page Section1 > {size:8.5in 11.0in; > margin:1.0in 32.35pt 1.0in 32.35pt;} > 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 link=3Dblue vlink=3Dpurple> > > <div class=3DSection1> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>Hi Lisa,<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>I guess it is important to have default disable iff apply to > nested modules also. Probably you can add some extra language to make that > clear along with your current suggestions. <o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>What do others think ?<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>Manisha<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <div> > > <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = > 0in 0in'> > > <p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma= > ","sans-serif"'>From:</span></b><span > style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lisa Piper > [mailto:piper@cadence.com] <br> > <b>Sent:</b> Friday, November 16, 2007 1:11 AM<br> > <b>To:</b> Kulshrestha, Manisha; sv-ac@eda.org<br> > <b>Subject:</b> RE: [sv-ac] 1648 - default disable iff<o:p></o:p></span></p> > > </div> > > </div> > > <p class=3DMsoNormal><o:p> </o:p></p> > > <p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif";color:= > blue'>Thanks > for reviewing this so promptly! I have some comments and questions be= > low. > <o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif";color:= > blue'><o:p> </o:p></span></p> > > <div> > > <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'> > > <hr size=3D2 width=3D"100%" align=3Dcenter> > > </div> > > <p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma= > ","sans-serif"'>From:</span></b><span > style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Kulshrestha, > Manisha [mailto:Manisha_Kulshrestha@mentor.com] <br> > <b>Sent:</b> Thursday, November 15, 2007 12:36 AM<br> > <b>To:</b> Lisa Piper; john.havlicek@freescale.com; sv-ac@eda.org<br> > <b>Subject:</b> RE: [sv-ac] 1648 - default disable iff</span><o:p></o:p></p> > > </div> > > <p class=3DMsoNormal><o:p> </o:p></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>Hi,<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>With the change in the name of default disable, I would like= > the > title of 16.15 to reflect that change i.e. change the title to ‘Defau= > lt > disable iff resolution’.<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif";color:= > blue'>[Lisa > Piper >>>] done<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'>I do not think that section 22.8 has any information about h= > ow > default disable iff should be resolved. It only deals with variable, task, > function, named block and generate blocks. So, how do we treat default disa= > ble > iff : like a variable declaration or a task declaration ? I think it is bet= > ter > to have scoping information in this section itself as default disable iff d= > oes > not behave like any of the above.<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= > "sans-serif"; > color:#1F497D'><o:p> </o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :11.0pt; > font-family:"Calibri","sans-serif";color:#1F497D'>There is another statement > “</span><span style=3D'font-size:10.0pt;color:#4527FF'>It provides a > default disable condition to all concurrent assertions in the scope of the > default </span><b><span style=3D'font-size:9.0pt;font-family:Courier;color:= > #4527FF'>disable > iff </span></b><span style=3D'font-size:10.0pt;color:#4527FF'>declaration,<= > o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:#4527FF'>in acco= > rdance > with the scope rules of 22.8.”. I am not sure which scoping rul= > es > are we referring to from 22.8 ?<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-fami= > ly:"Arial","sans-serif"; > color:blue'>[Lisa Piper >>>] I was mostly referring to: R= > 20;</span><span > style=3D'font-size:10.0pt;color:black'>If an identifier is referenced direc= > tly > (without a hierarchical path) within a task, function, named block, or<o:p>= > </o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>generate block, it shall be declared either within the task, > function, named block, or generate block locally or<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>within a module, </span><span style=3D'font-size:10.0pt;color:= > #B42F9F'>interface, > program, </span><span style=3D'font-size:10.0pt;color:black'>task, function, > named block, or generate block that is higher in the<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>same branch of the name tree that contains the task, function, > named block, or generate block. If it is<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>declared locally, then the local item shall be used; if not, t= > he > search shall continue upward until an item by<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>that name is found or until a module, </span><span > style=3D'font-size:10.0pt;color:#B42F9F'>interface, or program </span><span > style=3D'font-size:10.0pt;color:black'>boundary is encountered. If the item= > is a > variable,<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>it shall stop at a module boundary; if the item is a task, > function, named block, or generate block, it continues<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>to search higher level modules until found. This fact means th= > at > tasks and functions can use and modify the<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:black'>variables= > within > the containing module by name, without going through their </span><span > style=3D'font-size:10.0pt;color:#B42F9F'>formal arguments</span><span > style=3D'font-size:10.0pt;color:black'>.”<o:p></o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:black'><o:p>&nbs= > p;</o:p></span></p> > > <p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif";color:= > blue'>I > was picturing that you can declare a new “Default disable iff” = > in > any scope were a re-declaration is allowed, like a variable, and then this > applies. I guess with the BNF as it is, this is not true – it > cannot be defined in a named block or task or function.<o:p></o:p></span></= > p> > > <p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:black'><o:p>&nbs= > p;</o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>In the proposal it says: “</span><span style=3D'font-siz= > e: > 10.0pt;color:#4527FF'>Declaring more than one default </span><b><span > style=3D'font-size:9.0pt;font-family:Courier;color:#4527FF'>disable iff </s= > pan></b><span > style=3D'font-size:10.0pt;color:#4527FF'>item within the same module, inter= > face, > or program shall be an error.” . </span><span style=3D'font-size:10.0= > pt; > color:black'>This statement does not fit with the new scheme of allowing > default disable iff in generate blocks. Because effectively there may be > multiple declarations inside same module but they may be in generate block = > in > the module. <o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-fami= > ly:"Arial","sans-serif"; > color:blue'>[Lisa Piper >>>]. I can still re-use most of the > wording from 22.8: <o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-fami= > ly:"Arial","sans-serif"; > color:blue'><o:p> </o:p></span></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><i><span > style=3D'font-family:"Arial","sans-serif";color:blue'>Default disable iff</= > span></i><span > style=3D'font-family:"Arial","sans-serif";color:blue'> shall be declared ei= > ther > within a </span><s><span style=3D'font-family:"Arial","sans-serif";color:re= > d'>the > task, function, named block, or</span></s><span style=3D'font-family:"Arial= > ","sans-serif"; > color:blue'> generate block locally or<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><span > style=3D'font-family:"Arial","sans-serif";color:blue'>within a module, inte= > rface, > program</span><s><span style=3D'font-family:"Arial","sans-serif";color:red'= > >, > task, function, named block,</span></s><span style=3D'font-family:"Arial","= > sans-serif"; > color:blue'> or generate block that is higher in the<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><span > style=3D'font-family:"Arial","sans-serif";color:blue'>same branch of the na= > me > tree that contains it. </span><s><span style=3D'font-family:"Arial","sans-s= > erif"; > color:red'>the task, function, named block, or generate block</span></s><sp= > an > style=3D'font-family:"Arial","sans-serif";color:blue'>. If it is<o:p></o:p>= > </span></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><span > style=3D'font-family:"Arial","sans-serif";color:blue'>declared locally, the= > n the > local item shall be used; if not, the search shall continue upward until an > item by<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><span > style=3D'font-family:"Arial","sans-serif";color:blue'>that name is found or= > until > a module, interface, or program boundary is encountered. </span><span > style=3D'font-family:"Arial","sans-serif";color:fuchsia'>(so nested modules= > would > not be able to adopt the default disable of the top module – is this = > ok? > Should a default disable iff also apply to instances contained in the module > – I thought not since signals must be ports. ) </span><span > style=3D'font-family:"Arial","sans-serif";color:blue'><o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><span > style=3D'font-family:"Arial","sans-serif";color:blue'>More than one default > disable iff item within the same scope is an error. <o:p></o:p></span= > ></p> > > <p class=3DMsoNormal style=3D'margin-left:.5in;text-autospace:none'><span > style=3D'font-family:"Arial","sans-serif";color:blue'><o:p> </o:p></sp= > an></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-fami= > ly:"Arial","sans-serif"; > color:blue'>I thought of another interesting question. If I define my > default disable iff at my top level module to be a signal called reset, and > then I have a generate block within that defines its own reset signal but d= > oes > not re-define the default disable iff, then which reset signal is used? &nb= > sp;I > would assume it is the reset in the scope of the default disable iff > definition. Do you agree?<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'><o:p> </o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>I think referring to module, interface and program everywhere = > in > this paragraph is not right as default disable iff can be inside generates > also. <o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'><o:p> </o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'><o:p> </o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>Thanks.<o:p></o:p></span></p> > > <p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size= > :10.0pt; > color:black'>Manisha<o:p></o:p></span></p> > > <div> > > <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = > 0in 0in'> > > <p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma= > ","sans-serif"'>From:</span></b><span > style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> > owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] <b>On Behalf= > Of </b>Lisa > Piper<br> > <b>Sent:</b> Thursday, November 15, 2007 2:51 AM<br> > <b>To:</b> john.havlicek@freescale.com; sv-ac@server.eda.org<br> > <b>Subject:</b> [sv-ac] 1648 - default disable iff<o:p></o:p></span></p> > > </div> > > </div> > > <p class=3DMsoNormal><o:p> </o:p></p> > > <p class=3DMsoPlainText>The change was pretty simple as it turns out.<o:p><= > /o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText style=3D'margin-left:.5in'>A default disable iff ma= > y be > declared as an item within a module, interface, or program. It provides a > default disable condition to all concurrent assertions in the scope of the > default disable iff declaration, <span style=3D'color:blue'>in accordance w= > ith > the scope rules of 22.8.<o:p></o:p></span></p> > > <p class=3DMsoPlainText style=3D'margin-left:.5in'><o:p> </o:p></p> > > <p class=3DMsoPlainText>I made one other change. The label and section > number for 16.48 was wrong. It was a duplicate of the previous.<o:p><= > /o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>I did not make any other changes. I have uploaded i= > t to > Mantis.<o:p></o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>Lisa<o:p></o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>-----Original Message-----<br> > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of John > Havlicek<br> > Sent: Tuesday, November 13, 2007 9:22 PM<br> > To: sv-ac@eda.org<br> > Subject: [sv-ac] notes from SV-AC meeting 2007-11-13<o:p></o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>Hi Folks:<o:p></o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>My notes from today's meeting are attached.<o:p></o= > :p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>Please let me know if changes are required.<o:p></o= > :p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>J.H.<o:p></o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoPlainText>-- <o:p></o:p></p> > > <p class=3DMsoPlainText>This message has been scanned for viruses and<o:p><= > /o:p></p> > > <p class=3DMsoPlainText>dangerous content by MailScanner, and is<o:p></o:p>= > </p> > > <p class=3DMsoPlainText>believed to be clean.<o:p></o:p></p> > > <p class=3DMsoPlainText><o:p> </o:p></p> > > <p class=3DMsoNormal><br> > -- <br> > This message has been scanned for viruses and <br> > dangerous content by <a href=3D"http://www.mailscanner.info/"></b><b>MailSc= > anner</a>, > and is <br> > believed to be clean. <o:p></o:p></p> > > </div> > > </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_01C82B9C.F4718EBF-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Nov 20 10:15:56 2007
This archive was generated by hypermail 2.1.8 : Tue Nov 20 2007 - 10:16:11 PST