[sv-bc] Re: [sv-ec] Name resolution and imports

Gord,

As far as the question concerning immediate elevation to the
champions is concerned:

The mantis item should be addressed by the svbc first. If there is
a non-unanimous decision made by the svbc, it will be reviewed by
the champions. That is how the process has worked in the past and
I believe that is the intention of how it will continue to be.

Neil



Gordon Vreugdenhil wrote On 08/31/06 10:03,:
> All,
> 
> The name resolution working group has encountered an issue that
> needs to be resolved at the committee level.  The issue is directly
> addressed by Mantis 1323 -- "are imported names visible to
> hierarchical references".  Mentor and Cadence have both taken
> the position that they are not; Synopsys has taken the position
> that they are.  This needs to be resolved quickly as implementations
> have (and will continue) to diverge.  This also impacts the issue
> of chained imports (is a symbol imported into a package available
> for import) which is also addressed by Mantis 1323.
> 
> This issue has a direct bearing on back-annotation, pli, and
> related issues since it impacts what the system must present
> as members of a scope and whether hierarchical names for items
> in a design are unique or not.
> 
> Currently Mantis 1323 is listed as a BC issue.  I'd like to have
> this issue be resolved asap due to the overall impact of the
> interpretation differences.
> 
> Question:  should this immediately be elevated to the champions
> level or is it appropriate to leave for SV-BC?
> 
> Independent of that decision, it would be worthwhile for people
> to speak to this from various perspectives so that we can
> make an informed decision.
> 
> Gord