Section  28.4.3 Context tasks and functions (paragraph 2)

Replace

All DPI exported tasks or functions require that the context of their call is known. This occurs since SystemVerilog task or function declarations always occur in instantiable scopes, hence allowing a multiplicity of unique task or function instances. 

WITH

All DPI exported tasks or functions require that the context of their call is known. This occurs since SystemVerilog task or function declarations always occur in instantiable scopes, hence allowing a multiplicity of unique task or function instances.  .  The SystemVerilog context of DPI export tasks and functions must be known when they are called, including when they are called by imports.  When an import invokes the svSetScope utility prior to calling the export, it sets the context explicitly.  Otherwise, the context will be the context of the instantiated scope where the import declaration is located.  Since imports with diverse instantiated scopes can export the same task or function, multiple instances of such an export can exist after elaboration.  Prior to any invocations of svSetScope, these export instances would have different contexts, which would reflect their imported caller’s instantiated scope.

 

 

 

Section E.5.5 Context and non-context tasks and functions (par.3)

Replace

All DPI export tasks and functions require that the context of their call is known. This occurs since SystemVerilog task and function declarations always occur in instantiable scopes, hence allowing a multiplicity of unique task and function instances in the simulator’s elaborated database. Thus, there is no such thing as a non-context export task or function.

WITH

All DPI export tasks and functions require that the context of their call is known. This occurs since SystemVerilog task and function declarations always occur in instantiable scopes, hence allowing a multiplicity of unique task and function instances in the simulator’s elaborated database. Thus, there is no such thing as a non-context export task or function.  The SystemVerilog context of DPI export tasks and functions must be known when they are called, including when they are called by imports.  When an import invokes the svSetScope utility prior to calling the export, it sets the context explicitly.  Otherwise, the context will be the context of the instantiated scope where the import declaration is located.  Since imports with diverse instantiated scopes can export the same task or function, multiple instances of such an export can exist after elaboration.  Prior to any invocations of svSetScope, these export instances would have different contexts, which would reflect their imported caller’s instantiated scope.

 

 

Section  E.8.1 Overview of DPI and VPI context (paragraph 5)

Replace

Note that all DPI export tasks and functions require that the context of their call is known. This occurs since SystemVerilog task and function declarations always occur in instantiable scopes, hence giving rise to a multiplicity of associated task or function instances in the simulator’s database. Thus, there is no such thing as a non-context export tasks or function. All export task and function calls must have their execution scope specified in advance by use of a context-setting API function.

WITH

Note that all DPI export tasks and functions require that the context of their call is known. This occurs since SystemVerilog task and function declarations always occur in instantiable scopes, hence giving rise to a multiplicity of associated task or function instances in the simulator’s database. Thus, there is no such thing as a non-context export tasks or function. All export task and function calls must have their execution scope specified in advance by use of a context-setting API function..  The SystemVerilog context of DPI export tasks and functions must be known when they are called, including when they are called by imports.  When an import invokes the svSetScope utility prior to calling the export, it sets the context explicitly.  Otherwise, the context will be the context of the instantiated scope where the import declaration is located.  Since imports with diverse instantiated scopes can export the same task or function, multiple instances of such an export can exist after elaboration.  Prior to any invocations of svSetScope, these export instances would have different contexts, which would reflect their imported caller’s instantiated scope.