Static consistency checking for Verilog wire interconnects
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 such 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. 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 an open-source implementation demonstrating our approach.
KeywordsVerilog elaboration Static array bounds checking Verilog wire width consistency Dead code elimination Dependent types
Unable to display preview. Download preview PDF.
- 2.Gillenwater, J., Malecha, G., Salama, C., Zhu, A.Y., Taha, W., Grundy, J., O’Leary, J.: Synthesizable high level hardware descriptions: using statically typed two-level languages to guarantee Verilog synthesizability. In: PEPM ’08: Proceedings of the ACM SIGPLAN Symposium on Partial Evaluation and Semantics-Based Program Manipulation, New York, NY, USA, pp. 41–50. ACM, New York (2008) CrossRefGoogle Scholar
- 5.IEEE Standards Board. IEEE standard Verilog hardware description language. Number 1364-2001 in IEEE Standards. IEEE Press, New York (2001) Google Scholar
- 6.IEEE Standards Board. IEEE standard for Verilog hardware description language. Number 1364-2005 in IEEE Standards. IEEE Press, New York (2005) Google Scholar
- 7.Larochelle, D., Evans, D.: Statically detecting likely buffer overflow vulnerabilities. In: SSYM’01: Proceedings of the 10th Conference on USENIX Security Symposium, Berkeley, CA, USA. USENIX Association, Berkeley (2001). 14 pages Google Scholar
- 10.Taha, W.: Multi-stage programming: its theory and applications. PhD thesis, Oregon Graduate Institute of Science and Technology (1999) Google Scholar
- 11.Taha, W., Johann, P.: Staged notational definitions. In: Czarnecki, K., Pfenning, F., Smaragdakis, Y. (eds.) Generative Programming and Component Engineering (GPCE). Lecture Notes in Computer Science. Springer, Berlin (2003) Google Scholar
- 12.PolySpace Technologies. http://www.polyspace.com, 1999
- 14.Xi, H., Pfenning, F.: Eliminating array bound checking through dependent types. In: Proceedings of ACM SIGPLAN Conference on Programming Language Design and Implementation, Montreal, June 1998, pp. 249–257 (1998) Google Scholar