16.16 Disable iff resolution PAGE 403The LRM does not mention the legality of the declaration of a default disable iff in a checker. This seems to me like an error, as I see no reason as to why the checker should be excluded from this feature. I suggest that we add the checker. Since I cannot yet submit a mantis, Dmitry, please submit it for me. Change on page 403 from: A default disable iff may be declared within a generate block or within a module, interface, or program declaration. It provides a default disable condition to all concurrent assertions in the scope and subscopes of the default disable iff declaration. Furthermore, the default extends to any nested module, interface, or program declarations, and to nested generate blocks. However, if a nested module, interface, or program declaration, or a generate block itself has a default disable iff declaration, then that default disable iff applies within the nested declaration or generate block and overrides any default disable iff from outside. TO: A default disable iff may be declared within a generate block or within a module, interface, checker, or program declaration. It provides a default disable condition to all concurrent assertions in the scope and subscopes of the default disable iff declaration. Furthermore, the default extends to any nested module, interface, checker or program declarations, and to nested generate blocks. However, if a nested module, interface, checker or program declaration, or a generate block itself has a default disable iff declaration, then that default disable iff applies within the nested declaration or generate block and overrides any default disable iff from outside. ----------------- Ben Cohen -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed May 13 00:03:17 2009
This archive was generated by hypermail 2.1.8 : Wed May 13 2009 - 00:04:23 PDT