From: Charles Dawson (chas@cadence.com)
Date: Tue Jun 29 1999 - 09:55:44 PDT
--- Forwarded mail from <chas> ("Charles Dawson")
From: "Charles Dawson" <chas>
Date: Tue, 8 Jun 1999 11:43:49 -0400
To: PLI_TF
Subject: PTF 301
************************************************************************
PLI Task Force ID: PTF-301
Summary: Implement BTF enhancement B29 in PLI
(file and line compiler directives)
Relevant LRM Sections: ?
Current Status: Analyzed (pending Chas.)
Date Submitted: 22 Jan 1999
Date Analyzed: 24 May 1999
Date of Last Action: 24 May 1999
Author of Submission: Stuart Sutherland
Author's Net Address: stuart@sutherland.com
Description of Problem:
22 Jan 1999: This enhancement to Verilog has been approved by the BTF.
Need to implement in the PLI.
17 may 1999: The enhancement has been officially approved by the 1364
working group.
Proposed Resolution:
24 May 1999: Assigned to Chas. to propose changes required in LRM.
TF Recommendation for changes to 1364-1995 standard:
03 Jun 1999:
I propose making the following changes to support this BTF enhancement:
<p> 1. Since almost all objects have a location, we should remove these
properties from the diagrams (just like vpiType is not in the
diagrams), and create a new sub-section in section 22.2.1 as follows:
22.2.1.1 Default Properties
Some properties apply to every object, and therefore are not illustrated
in section 22.5. Specifically, the property
-> type
int: vpiType
can be used on every object. Note, that this property can also be
accessed as a string using vpi_get_str(). Other properties which
are not listed are location properties:
-> location
int: vpiLineNo
str: vpiFile
int: vpiOrigLineNo
str: vpiOrigFile
int: vpiLevel
The properties vpiOrigLineNo, vpiOrigFile, and vpiLevel are only
applicable if there is a `line compiler directive associated with the
object. If there is no `line compile directive then the following
values will be returned for each property, without an error being
generated:
vpiOrigLineNo will return vpiUndefined
vpiOrigFile will return NULL
vpiLevel will return vpiUndefined
These properties are applicable to every object that corresponds to
some object within the HDL. The exceptions are objects of type:
vpiCallback
vpiDelayTerm
vpiDelayDevice
vpiInterModPath
vpiTimeQueue
2. Add the following properties to the module object:
-> definition location
int: vpiDefOrigLineNo
str: vpiDefOrigFile
int: vpiDefLevel
<p><p><p>---End of forwarded mail from <chas> ("Charles Dawson")
Content-Type: text/plain ; name="PTF-301.txt" ; name=PTF-301.txt ; charset=us-ascii
Content-Disposition: attachment ; filename="PTF-301.txt"
X-Zm-Content-Name: PTF-301.txt
Attachment Converted: "E:\INCOMING\PTF-301.txt"
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:53:28 PDT
and
sponsored by Boyd Technology, Inc.