ACM Home Page
Please provide us with feedback. Feedback
Synthesizable high level hardware descriptions: using statically typed two-level languages to guarantee verilog synthesizability
Full text PdfPdf (244 KB)
Source
ACM/SIGPLAN Workshop Partial Evaluation and Semantics-Based Program Manipulation archive
Proceedings of the 2008 ACM SIGPLAN symposium on Partial evaluation and semantics-based program manipulation table of contents
San Francisco, California, USA
SESSION: Verification and synthesis table of contents
Pages 41-50  
Year of Publication: 2008
ISBN:978-1-59593-977-7
Authors
Jennifer Gillenwater  Rice University, Houston, TX
Gregory Malecha  Rice University, Houston, TX
Cherif Salama  Rice University, Houston, TX
Angela Yun Zhu  Rice University, Houston, TX
Walid Taha  Rice University, Houston, TX
Jim Grundy  Intel Strategic CAD Labs, Portland, OR
John O'Leary  Intel Strategic CAD Labs, Portland, OR
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
SIGACT: ACM Special Interest Group on Algorithms and Computation Theory
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 54,   Citation Count: 1
Additional Information:

abstract   references   cited by   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/1328408.1328416
What is a DOI?

ABSTRACT

Modern hardware description languages support code-generation constructs like generate/endgenerate in Verilog. These constructs are intended to describe regular or parameterized hardware designs and, when used effectively, can make hardware descriptions shorter, more understandable, and more reusable. In practice, however, designers avoid these constructs because it is difficult to understand and predict the properties of the generated code. Is the generated code even type safe? Is it synthesizable? What physical resources (e.g. combinatorial gates and flip-flops) does it require? It is often impossible to answer these questions without first generating the fully-expanded code. In the Verilog and VHDL communities, this generation process is referred to as elaboration.

This paper proposes a disciplined approach to elaboration in Verilog. By viewing Verilog as a statically typed two-level language, we are able to reflect the distinction between values that are known at elaboration time and values that are part of the circuit computation. This distinction is crucial for determining whether abstractions such as iteration and module parameters are used in a synthesizable manner. To illustrate this idea, we develop a core calculus for Verilog that we call Featherweight Verilog (FV) and an associated static type system. We formally define a preprocessing step analogous to the elaboration phase of Verilog, and the kinds of errors that can occur during this phase. Finally, we show that a well-typed design cannot cause preprocessing errors, and that the result of its expansion is always a synthesizable circuit.


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
Henk P. Barendregt. The Lambda Calculus: Its Syntax and Semantics, volume 103 of Studies in Logic and the Foundations of Mathematics. North-Holland, Amsterdam, 1984.
 
2
Bluespec, Inc. Bluespec SystemVerilog Version 3.8 Reference Guide, 2006.
 
3
Jennifer Gillenwater, Gregory Malecha, Cherif Salama, Angela Yun Zhu, Walid Taha, Jim Grundy, and John O'Leary. Synthesizable High Level Hardware Descriptions. Technical report, Rice University and Intel Strategic CAD Labs, http://www.resourceaware.org/twiki/pub/RAP/VPP/FV-TR.pdf, 2007.
 
4
Carsten K. Gomard and Neil D. Jones. A partial evaluator for the untyped lambda-calculus. Journal of Functional Programming, 1(1):21--69, 1991.
 
5
IEEE Standards Board. IEEE Standard Hardware Description Language Based on the Verilog Hardware Description Language. Number 1364--1995 in IEEE Standards. IEEE, 1995.
 
6
IEEE Standards Board. IEEE Standard Verilog Hardware Description Language. Number 1364--2001 in IEEE Standards. IEEE, 2001.
 
7
IEEE Standards Board. IEEE Standard for SystemVerilog-Unified Hardware Design, Specification, and Verification Language. Number 1800--2005 in IEEE Standards. IEEE, 2005.
 
8
IEEE Standards Board. IEEE Standard for Verilog Hardware Description Language. Number 1364--2005 in IEEE Standards. IEEE, 2005.
 
9
IEEE Standards Board. IEEE Standard for Verilog Register Transfer Level Synthesis. Number 1364.1--2002 (IEC 62142:2005) in IEEE Standards. IEEE, 2005.
10
11
 
12
Sun Microsystems. Opensparc t1 processor file: mul64.v. http://opensparc-t1.sunsource.net/nonav/source/verilog/html/mul64.v.
 
13
 
14
Opencores.org. Or1200's 32x32 multiply for asic. http://www.opencores.org/cvsweb.shtml/or1k/or1200/rtl/verilog/or1200 amultp2 32x32.v.
 
15
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.
 
16
Walid Taha. Multi-Stage Programming: Its Theory and Applications. PhD thesis, Oregon Graduate Institute of Science and Technology, 1999. available from {15}.
 
17
Walid Taha, Stephan Ellner, and Hongwei Xi. Generating imperative, heap--bounded programs in a functional setting. In Proceedings of the Third International Conference on Embedded Software, Philadelphia, PA, 2003.
 
18
Walid Taha and Patricia Johann. Staged notational definitions. In Krzysztof Czarnecki, Frank Pfenning, and Yannis Smaragdakis, editors, Generative Programming and Component Engineering (GPCE), Lecture Notes in Computer Science. Springer-Verlag, 2003.
 
19
Terese. Term Rewriting Systems. Cambridge University Press, 2003.


Collaborative Colleagues:
Jennifer Gillenwater: colleagues
Gregory Malecha: colleagues
Cherif Salama: colleagues
Angela Yun Zhu: colleagues
Walid Taha: colleagues
Jim Grundy: colleagues
John O'Leary: colleagues