You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to support verification flow (and UVM) there is a need to support both
importmy_pkg::* ;
importmy_pkg::foo;
Those are managed by, respectively, WildcardImportSymbol and ExplicitImportSymbol.
Explicit import
Explicit import provides a link to the imported symbol. Hence it should be easy to get back the source range, find the undelying IndexSymbol and link.
As of today, the ExplicitImportSymbol is recorded as a new symbol and the local references are bound to it. This will need to be avoided.
Implicit import
Implicit import can lead to the imported (Slang) scope. It can probably be possible to visit this scope and add all symbols definitions to the using file...
As the package is also present from the top of the index structure, it should be possible to simply add the package name as a lookup location for symbols during the reference matching process.
This should be done on a per-file basis.
The text was updated successfully, but these errors were encountered:
In order to support verification flow (and UVM) there is a need to support both
Those are managed by, respectively,
WildcardImportSymbol
andExplicitImportSymbol
.Explicit import
Explicit import provides a link to the imported symbol. Hence it should be easy to get back the source range, find the undelying
IndexSymbol
and link.As of today, the
ExplicitImportSymbol
is recorded as a new symbol and the local references are bound to it. This will need to be avoided.Implicit import
Implicit import can lead to the imported (Slang) scope. It can probably be possible to visit this scope and add all symbols definitions to the using file...
As the package is also present from the top of the index structure, it should be possible to simply add the package name as a lookup location for symbols during the reference matching process.
This should be done on a per-file basis.
The text was updated successfully, but these errors were encountered: