Proceedings. IEEE International Verilog HDL Conference
DOI: 10.1109/ivc.1996.496013
|View full text |Cite
|
Sign up to set email alerts
|

The Verilog Procedural Interface for the Verilog Hardware Description Language

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 17 publications
(8 citation statements)
references
References 0 publications
0
8
0
Order By: Relevance
“…If there are more than three, only the first three should be given followed by et al Please provide the missing author names in Refs. [1,2,4,5,6,7,8,9,10,11,13,14,16,17,18,19,20,21].…”
Section: Q4mentioning
confidence: 99%
“…If there are more than three, only the first three should be given followed by et al Please provide the missing author names in Refs. [1,2,4,5,6,7,8,9,10,11,13,14,16,17,18,19,20,21].…”
Section: Q4mentioning
confidence: 99%
“…In our view, the designer of a new queuemanagement algorithm would be better off accessing these primitives through a high-level procedural language, such as C++, through the Verilog Procedural Interface [8].…”
Section: What Interface Should the Switch Expose?mentioning
confidence: 99%
“…While the µarch-level simulator can access the named pipes like files, the gate-level simulator is enhanced with two system tasks, implemented using the Verilog Procedural Interface (VPI) [9], that handle accesses to/from the pipes: One collects signals from the stimuli pipe and the other writes the results to the response pipe. The stimuli and response (arguments of the two tasks) are tailored to the µarch-level structures under fault injection.…”
Section: Interfacing the Simulatorsmentioning
confidence: 99%