Lisa, I do not assume that any section of the LRM is owned by any particular subcommittee. Technically, the LRM is "owned" by the Working Group and the subcommittees are task forces made up of people with local areas of expertise. Generally my preference is to have the subcommittee that wrote the text fix it, but if this is out of your area of expertise, the sv-ec should take it up. Dave > -----Original Message----- > From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On > Behalf Of Lisa Piper > Sent: Monday, October 08, 2007 6:01 AM > To: Bresticker, Shalom; sv-ac@server.eda-stds.org; sv-ec@server.eda.org > Subject: [sv-ec] RE: [sv-ac] hierarchical references into programs > > Shalom, > > Who is responsible for taking care of this? My understanding was that > after 1722 this section (22.10) would be owned by sv-bc. Is that > correct? > > Lisa > > -----Original Message----- > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of > Bresticker, Shalom > Sent: Friday, October 05, 2007 6:44 AM > To: sv-ac@eda-stds.org; sv-ec@eda.org > Subject: [sv-ac] hierarchical references into programs > > Hi, > > I corresponded with Gord a few months ago about the following issue: > > All the references are to Draft 4: > > 23.5 says, > "Calling program tasks or functions from within design modules is > illegal and shall result in an error." > > (Probably the word 'design' should be stricken as there is no concept of > 'design modules' and 'non-design module'. > > 23.3 says, > "References to program signals from outside any program block shall be > an error." > > 23.6 says, > "The set of program definitions and instances define a space of > programwide data, tasks, and functions that is accessible only to > programs." > > Thus, in Gord's words: "The LRM does not allow ANY hierarchical > references from modules to programs." > > Yet, 22.10 says, > "By binding a program to a module or an instance, the program becomes > part of the bound object. The names of assertion-related declarations > can be referenced using the SystemVerilog hierarchical naming > conventions." > > In the context, the meaning seems to be that the 'assertion-related > declarations' (whatever that means) are in the program, and the > hierarchical reference is from outside the program to inside the > program. > > This is illegal, however. > > Thus, this statement in 22.10 should be changed. Gord suggests adding > the following sentence in 22.10: > > "Hierarchical references to an item in a bound instance are permitted > following normal hierarchical naming rules." > > Thanks, > Shalom > --------------------------------------------------------------------- > Intel Israel (74) Limited > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Oct 8 09:06:19 2007
This archive was generated by hypermail 2.1.8 : Mon Oct 08 2007 - 09:06:49 PDT