ACM Home Page
Please provide us with feedback. Feedback
Static consistency checking for verilog wire interconnects: using dependent types to check the sanity of verilog descriptions
Full text PdfPdf (562 KB)
Source
ACM/SIGPLAN Workshop Partial Evaluation and Semantics-Based Program Manipulation archive
Proceedings of the 2009 ACM SIGPLAN workshop on Partial evaluation and program manipulation table of contents
Savannah, GA, USA
SESSION: Types table of contents
Pages 121-130  
Year of Publication: 2009
ISBN:978-1-60558-327-3
Authors
Cherif Salama  Rice University, Houston, TX, USA
Gregory Malecha  Rice University, Houston, TX, USA
Walid Taha  Rice University, Houston, TX, USA
Jim Grundy  Intel Strategic CAD Labs, Portland, OR, USA
John O'Leary  Intel Strategic CAD Labs, Portland, OR, USA
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 32,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1480945.1480963
What is a DOI?

ABSTRACT

The Verilog hardware description language has padding semantics that allow designers to write descriptions where wires of different bit widths can be interconnected. However, many of these connections are nothing more than bugs inadvertently introduced by the designer and often result in circuits that behave incorrectly or use more resources than required. A similar problem occurs when wires are incorrectly indexed by values (or ranges) that exceed their bounds. These two problems are exacerbated by generate blocks. While desirable for reusability and conciseness, the use of generate blocks to describe circuit families only makes the situation worse as it hides such inconsistencies making them harder to detect. Inconsistencies in the generated code are only exposed after elaboration when the code is fully-expanded.

In this paper we show that these inconsistencies can be pinned down prior to elaboration using static analysis.We combine dependent types and constraint generation to reduce the problem of detecting the aforementioned inconsistencies to a satisfiability problem. Once reduced, the problem can easily be solved with a standard satisfiability modulo theories (SMT) solver. In addition, this technique allows us to detect unreachable code when it resides in a block guarded by an unsatisfiable set of constraints. To illustrate these ideas, we develop a type system for Featherweight Verilog (FV), a core calculus of structural Verilog with generative constructs and previously defined elaboration semantics. We prove that a well-typed FV description will always elaborate into an inconsistency-free description. We also provide a freely-available implementation demonstrating our approach.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
B. Dutertre and L. de Moura. The Yices SMT solver. Tool paper at http://yices.csl.sri.com/tool-paper.pdf, August 2006.
2
 
3
Carsten K. Gomard and Neil D. Jones. A partial evaluator for the untyped lambda-calculus. Journal of Functional Programming, 1(1):21--69, 1991.
4
 
5
IEEE Standards Board. IEEE Standard Verilog Hardware Description Language. Number 1364-2001 in IEEE Standards. IEEE, 2001.
 
6
IEEE Standards Board. IEEE Standard for Verilog Hardware Description Language. Number 1364-2005 in IEEE Standards. IEEE, 2005.
 
7
 
8
 
9
Oregon Graduate Institute Technical Reports. P.O. Box 91000, Portland, OR 97291-1000, USA. Available online from: ftp://cse.ogi.edu/pub/tech-reports/README.html.
 
10
Cherif Salama, Gregory Malecha, Walid Taha, Jim Grundy, and John O'Leary. Static consistency checking for Verilog wire interconnects. Technical report, Rice University and Intel Strategic CAD Labs, http://www.resource-aware.org/twiki/pub/RAP/VPP/FVTR2.pdf, 2008.
 
11
 
12
 
13
PolySpace Technologies. http://www.polyspace.com.
14
15

Collaborative Colleagues:
Cherif Salama: colleagues
Gregory Malecha: colleagues
Walid Taha: colleagues
Jim Grundy: colleagues
John O'Leary: colleagues