| Add Proposal | Edit Analysis | Edit Class, Environment, or Release |
| Number | 68
|
| Category | errata
|
| Synopsis | Missing objects from VPI attribute object diagram
|
| State | analyzed
|
| Class | errata-ptf
|
| Arrival-Date | Jan 31 2002
|
| Originator | Dennis Marsa
|
| Release | 2001b: 26.6.42
|
| Environment |
|
| Description |
In Section 26.6.42, which shows the VPI object diagram for "attribute" objects, the following VPI objects are missing from the dotted class on the left side of the diagram: "iodecl" "cont assign" "defparam" Each of these types of objects can have attributes attached to them according to the BNF of Annex A. |
| Fix |
Will need the PLI task force to review this one. |
| Audit-Trail |
From: Dennis Marsa <drm@xilinx.com> To: ptf-bugs@boyd.com Cc: Subject: Re: errata/68: Missing objects from VPI attribute object diagram Date: Fri, 21 Mar 2003 15:37:26 -0700 drm@xilinx.com wrote: > > Precedence: bulk > > >Number: 68 > >Category: errata > >Originator: Dennis Marsa > >Description: > > In Section 26.6.42, which shows the VPI object diagram > for "attribute" objects, the following VPI objects are > missing from the dotted class on the left side of the > diagram: > > "iodecl" > "cont assign" > "defparam" > > Each of these types of objects can have attributes > attached to them according to the BNF of Annex A. Here is a more detailed analysis of this issue. There are actuall several sub-issues. 1) There are VPI objects whose corresponding syntax allows attributes but are not shown in the diagram of 26.6.42. These VPI objects are: vpiIODecl vpiContAssign vpiDefParam vpiParameter vpiNetArray vpiRegArray vpiNamedEventArray vpiPrimitiveArray vpiModuleArray vpiFuncCall This sub-issue can be resolved by adding the above listed objects to the diagram of 26.6.52. 2) There are VPI objects shown in the diagram of 26.6.42 whose corresponding syntax DOES NOT allow attributes. These VPI objects are: vpiPort vpiPrimTerm vpiPathTerm vpiModPath vpiTchk vpiParamAssign vpiTableEntry To resolve this sub-issue we must determine for each object if: a) it is erroneously listed in 26.6.42, or b) the BNF rules for this object erroneously omit attribute syntax 3) There are syntactic elements which allows attributes which do not have any VPI object to represent them. These syntactic elements (BNF rules) are: generated_instantiation genvar_declaration specify_block To resolve this sub-issue, we must first determine if it makes sense to attach attributes to these constructs. Second, if it is does make sense, to what existing/new VPI objects will the attributes be attached to, or if it does not make sense, correct the BNF to not allow attribute syntax for these constructs. Dennis Marsa Xilinx, Inc. |
| Unformatted |
|
Hosted by Boyd Technology