Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
config:runtime [2023/01/31 00:13] – [Decomposition passes] rajit | config:runtime [2025/05/27 18:12] (current) – [Verilog global signal prefix] rajit | ||
---|---|---|---|
Line 32: | Line 32: | ||
</ | </ | ||
This specifies a limit on array sizes that also have internal sub-connections (i.e. arrays that are not just simple memories, for example). The limit should be increased as needed, but can have a performance impact if you have a very large array with internal sub-connections. | This specifies a limit on array sizes that also have internal sub-connections (i.e. arrays that are not just simple memories, for example). The limit should be increased as needed, but can have a performance impact if you have a very large array with internal sub-connections. | ||
- | |||
- | ===== Attributes ===== | ||
- | |||
- | ACT supports attributes on both instances and production rules. An ACT instance can be assigned an attribute in the following way: | ||
- | |||
- | <code act> | ||
- | bool v @ [attr=0]; | ||
- | bool w; | ||
- | w @ [attr=5]; | ||
- | </ | ||
- | In these two examples, the signal '' | ||
- | |||
- | < | ||
- | begin act | ||
- | string_table instance_attr " | ||
- | end | ||
- | </ | ||
- | |||
- | This specifies three instance attributes: '' | ||
- | * The first component ''// | ||
- | * The second component ''// | ||
- | * '' | ||
- | * '' | ||
- | * '' | ||
- | * '' | ||
- | * '' | ||
- | * ''&'': | ||
- | |||
- | A second set of attributes can be specified per-production rule. | ||
- | |||
- | < | ||
- | string_table prs_attr " | ||
- | </ | ||
- | The syntax for these is the same, except the attributes are applied per production rule. These attributes are interpreted by the [[tools: | ||
Line 127: | Line 93: | ||
</ | </ | ||
- | ===== Verilog Global Prefix ===== | ||
- | Since ACT can refer to global signals, this functionality may be needed when converting ACT files into Verilog | + | |
+ | ===== External Black Box Support ===== | ||
+ | |||
+ | ACT also provides a mechanism for "black box" modules---components that are defined elsewhere, like external hard macros. We assume that the external specification of the macros includes: | ||
+ | * A LEF file, for layout generation, along with bounding box information in the LEF coordinate system | ||
+ | * A SPICE file, for circuit simulation | ||
+ | * A Verilog | ||
+ | * TBD | ||
+ | |||
+ | A process is treated as a black box if it is defined with an empty body. For example: | ||
+ | |||
+ | <code act> | ||
+ | defproc bbproc (bool? A, B, C; bool! D) { } | ||
+ | </ | ||
+ | is interpreted as a black box by default. (Note that there is a configuration parameter that can be used to turn off this behavior, in which case this component will be eventually stripped out of the design since it does not contain any circuit component.) | ||
+ | |||
+ | The location of the LEF/SPICE/Verilog/etc. for the black box must be included in an ACT configuration file using the following configuration section: | ||
< | < | ||
- | begin act | + | begin macros |
- | string | + | begin < |
+ | string lef " | ||
+ | | ||
+ | string verilog " | ||
+ | int llx < | ||
+ | int lly < | ||
+ | int urx < | ||
+ | int ury < | ||
+ | end | ||
end | end | ||
</ | </ | ||
- | This specifies that a global signal | + | The expanded name is the fully expanded name for the process (in this case '' |
+ | |||
+ | ==== Generalized External Black Box ==== | ||
+ | |||
+ | Sometimes we require a more sophisticated model for an external black box. In particular, we might want to specify internal nodes within the black box so that the timing model for the black box can be made more precise. For this purpose, a more general black box syntax is supported. | ||
+ | |||
+ | <code act> | ||
+ | defproc bbproc (bool? A, B, C; bool! D) { bool int1, int2; } | ||
+ | </ | ||
+ | This process will also be treated as a black box, but with the understanding that there are also internal nodes that might be used to build a more sophisticated timing model. | ||
+ | A generalized black box body can only contain instances of signals that are of type '' |