Download EXPRESSION User Manual version 1.0

Transcript
A.4. Components
This subsection describes each RT level component in the architecture. The
components can be any of Pipeline units, Functional units, Storage elements,
Ports and Connections. Each component also has a list of attributes
(optional). The attributes can be any of the following:
SUBCOMPONENTS: If the component is a compound component, specifies
the list of subcomponents.
LATCHES: If the component is a unit, specifies the list of latches that the
unit is attached to.
PORTS: The list of ports attached to this component.
CONNECTIONS: The list of connections attached to this component.
OPCODES: The list of opcode groups that this component accepts. (Note: If
this attribute is all then it means that the component does not make a
distinction between opcodes.)
TIMING: For multi cycle or pipelined units, specifies the timing behavior.
Timing can be specified on a per opcode basis if necessary.
CAPACITY: The number of operations that can be accepted by this
component in a single cycle. The default is a single operation per cycle.
A.5. Pipeline and Data Transfer Paths
This subsection describes the net-list of the processor. The pipeline
description provides a mechanism to specify the units that comprise the
pipeline stages, while the data-transfer paths description provides a
mechanism for specifying the valid data-transfers. This information is used
to both retarget the simulator, and to generate reservation tables needed by
the scheduler.
The pipeline paths and the data transfers represent the structural net-list
information for the architecture. They can be generated automatically from a
schematic capture tool. When writing/generating this information, false
paths may be present in the architecture. This problem is solved by the fact
that besides the net-list, behavioral information is also present. False paths
due to illegal operations will never be activated, since the illegal operations
are omitted from the description. False paths due to illegal groups of
operations (either in sequence or in parallel) can be tackled by either
specifying the common resource used by the operations to raise a conflict in
76
EXPRESSION User Manual
© 2003 ACES Laboratory