[vhdl-200x-ft] FW: 'PATHNAME 'INSTANCENAME attribute specifications

  _____

From: owner-vhpi-pilot@eda.org [mailto:owner-vhpi-pilot@eda.org] On Behalf
Of Francoise Martinolle
Sent: Monday, February 14, 2005 10:56 AM
To: vhdl200x-ft@eda.org
Cc: vhpi-pilot@eda.org
Subject: 'PATHNAME 'INSTANCENAME attribute specifications

Jim and other vhdl200x-ft,
 
The VHPI LRM was sent to a few experts for review.
We have received some of the review comments for VHPI.
One review comment was an objection against specifying the names of
implicit labels. The reviewer said that this should be fixed im VHDL 200x.
We feel that VHPI outght to provide unambiguous names for lookup
capabilities,
hence VHPI specified a standard way of naming implicit labels where it
matters (loops, process, generates).
 
I would like to know if enhancing 'pathname and 'instancename has been
considered
by vhdl 200x.
 
Below is the problem and action requested as well as the VHPI task force
response:
 
Problem:
 
The rules for implicit labels over specify what is required for a
reasonable VHPI functionality. It is important to support unique name
lookup but it is not necessary to impose the same convention on all
tools. If that is truly desired, then the change should be made to
define those conventions as part of the base language and correct the
underlying name attributes `PATHNAME and `INSTANCENAME.
 
Action:
 
Require tool providers to generate unique labels where statement
labels are optional but affect name properties and lookup as defined
in this section. Only require that handle-by-name work consistently
with names of objects returned by this tool. Alternatively, make the
fix to the base language to define implicit labels such that objects
will have unique names reflected in pre-defined name attributes.
 

REVIEWER'S COMMENTS
 
Accept: We will ask the vhdl 200x-ft to fix the 'PATHNAME and
'INSTANCENAME attribute specifications to be unambiguous for the cases
where it matters. However if the vhdl200x rejects the enhancement of
these attributes, there is merit in VHPI having these names
unambiguous for tool interoperability.

 
 
Received on Mon Feb 14 08:25:34 2005