| Anonymous | Login | 2010-09-03 01:57 PDT |
| Main | My View | View Issues | Docs | Wiki |
| Viewing Issue Simple Details [ Jump to Notes ] [ Wiki ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Date Submitted | Last Update | |||
| 0000594 | [SystemVerilog P1800] SV-EC | major | 2005-03-23 17:29 | 2008-05-14 23:41 | |||
| Reporter | Steven Sharp | View Status | public | ||||
| Assigned To | doug_warmke | ||||||
| Priority | immediate | Resolution | fixed | ||||
| Status | closed | Product Version | |||||
| Summary | 0000594: 15.8 special syntax for accessing interfaces through clocking block | ||||||
| Description |
Erratum entered for another reviewer. Section 15.8 describes in great detail a special syntax for use in accessing items within interfaces through a clocking block. Unfortunately, this special syntax is not supported by the BNF. Further, it would be inadvisable for the BNF to support this special syntax. Essentially the syntax allows a hierarchical identifier to be used in defining a local clockvar variable. This significantly breaks the entire concept of using '.' as a separator between scope or members. Rather than have such a special syntax this semantic functionality can simply be achieved through the use of a hierarchical identifier as described by section 15.4. We can, however, understand that the user may wish to have special syntax used for interacting with interfaces. A much more consistent way to achieve this would be to follow the standard scoping rules of Verilog and create an additional sub-scope within a clocking block. In fact we could even re-use the keyword interface to achieve this. Broken Example: module M(interface I, wire clk); clocking block @(clk); input I.signal; // broken syntax endclocking endmodule Recommended Syntax to achieve the same functionality: module M(interface I, wire clk); clocking block @(clk); interface I; input signal; // working syntax endinterface; endclocking endmodule Note that if the above recommendation can not be achieved, then the next best recommendation is to remove section 15.8 from the LRM and simply use the functionality of section 15.4 to access within interfaces. It is not recommended that we attempt to footnote this or somehow squeeze it into the BNF. |
||||||
| Additional Information |
Approved on October/9/2006 unanimously. 594_1.pdf is approved. Updated Status/Resolution field according to SV_DB_process guide. Resolved.Fixed. Text change/addition. |
||||||
| Tags | No tags attached. | ||||||
| Type | Errata | ||||||
| Attached Files |
|
||||||
|
|
|||||||
| Mantis 1.1.7[^] Copyright © 2000 - 2008 Mantis Group |