TY - JOUR
T1 - Behavioural synthesis utilising recursive definitions
AU - Brown, A. D.
AU - Milton, D. J. D.
AU - Rushton, A. J.
AU - Wilson, P. R.
PY - 2012/11
Y1 - 2012/11
N2 - Behavioural synthesis is the process of automatically translating an abstract specification to physical realisation - silicon. The endpoints of this process are accelerating apart (behavioural descriptions become more abstract, DSM silicon becomes less willing to behave as Boolean circuits) but there is still work outstanding in the middle ground. Recursion allows the elegant expression of complicated systems, and is supported by many languages (software and hardware). The electronic design automation (EDA) tool designers- task is to support the semantics of a language (both simulation and synthesis). Although recursive descriptions can always be re-cast into non-recursive iterative forms, if a language supports a construct, a user should be able to utilise it (the authors are not offering any opinion on the relative wisdom of using recursion or iteration). The authors describe the problems/solutions of supporting the semantics of recursion (single/multiple, direct/arbitrarily indirect) in synthesis. The hardware synthesised can be smaller and faster than that obtained by reformulating the description. It is dangerous, to conclude too much from this - recursion requires a stack and a heap (plus managers). In software, these are taken for granted (-free- resources that do not feature in footprint metrics); in hardware, every resource needed must be explicitly created.
AB - Behavioural synthesis is the process of automatically translating an abstract specification to physical realisation - silicon. The endpoints of this process are accelerating apart (behavioural descriptions become more abstract, DSM silicon becomes less willing to behave as Boolean circuits) but there is still work outstanding in the middle ground. Recursion allows the elegant expression of complicated systems, and is supported by many languages (software and hardware). The electronic design automation (EDA) tool designers- task is to support the semantics of a language (both simulation and synthesis). Although recursive descriptions can always be re-cast into non-recursive iterative forms, if a language supports a construct, a user should be able to utilise it (the authors are not offering any opinion on the relative wisdom of using recursion or iteration). The authors describe the problems/solutions of supporting the semantics of recursion (single/multiple, direct/arbitrarily indirect) in synthesis. The hardware synthesised can be smaller and faster than that obtained by reformulating the description. It is dangerous, to conclude too much from this - recursion requires a stack and a heap (plus managers). In software, these are taken for granted (-free- resources that do not feature in footprint metrics); in hardware, every resource needed must be explicitly created.
UR - http://dx.doi.org/10.1049/iet-cdt.2012.0006
U2 - 10.1049/iet-cdt.2012.0006
DO - 10.1049/iet-cdt.2012.0006
M3 - Article
SN - 1751-861X
VL - 6
SP - 362
EP - 369
JO - IET Computers and Digital Techniques
JF - IET Computers and Digital Techniques
IS - 6
ER -