Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
language:langs:start [2022/06/29 15:03]
rajit [Auxillary sub-languages]
language:langs:start [2022/07/11 07:43] (current)
rajit [Auxillary sub-languages]
Line 25: Line 25:
 The refinement body is simply a standard ACT body. When the refinement body is selected, the other circuit languages are omitted. Similarly when one of CHP/HSE/PRS are selected, the refinement body is omitted. The refinement body can be selected using the ''-ref=N'' [[stdoptions:start|command-line option]] for any ACT tool. The refinement body is simply a standard ACT body. When the refinement body is selected, the other circuit languages are omitted. Similarly when one of CHP/HSE/PRS are selected, the refinement body is omitted. The refinement body can be selected using the ''-ref=N'' [[stdoptions:start|command-line option]] for any ACT tool.
  
-===== Auxillary sub-languages =====+===== Auxiliary sub-languages ===== 
 + 
 +Auxiliary sub-languages augment the circuit specification in some way. The sizing sub-language can be used to specify gate sizing directives that apply to the ''prs'' sub-language.  The ''spec'' sub-language can be used to apply a range of directives to Boolean-valued variables. These directives include timing requirements, mutual exclusion requirements, and specifications of signals that can have switching hazards.
  
   * [[sizing|Gate sizing directives]]   * [[sizing|Gate sizing directives]]
Line 38: Line 40:
   * device, which corresponds to the transistor-level implementation of the gates. The device level doesn't have an explicit syntax, as the PRS language has enough detail to be able to capture this level of abstraction.   * device, which corresponds to the transistor-level implementation of the gates. The device level doesn't have an explicit syntax, as the PRS language has enough detail to be able to capture this level of abstraction.
  
 +A configuration file can be specified that selects the level of detail for a process  type / instance name. This file is typically passed via the command-line option ''-cnf=file.conf'' to ACT tools. The parameters you can specify are:
 +
 +<code>
 +begin level
 +# valid strings are "chp", "hse", "prs", and "device"
 +   string default "chp"
 +end
 +</code>   
 +This specifies the default level selected for every process. (Dataflow is treated as fine-grained parallel CHP.)
  
 +<code>
 +begin level
 +   begin types
 +   # chp process model
 +     string_table chp "procname<5>"  "proc2<>"
 +   # prs process model
 +     string_table prs "proc3<>"
 +   end
 +end
 +</code>
 +This specifies that the particular process names should be modeled at the specified level of abstraction.