Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] View of /sml/trunk/src/MLRISC/Doc/latex/instructions.tex
ViewVC logotype

View of /sml/trunk/src/MLRISC/Doc/latex/instructions.tex

Parent Directory Parent Directory | Revision Log Revision Log

Revision 651 - (download) (as text) (annotate)
Thu Jun 1 18:34:03 2000 UTC (20 years, 5 months ago) by monnier
File size: 3187 byte(s)
bring revisions from the vendor branch to the trunk

  Instructions in MLRISC are implemented as abstract datatypes and
must satisfy the signature 
\mlrischref{instructions/instructions.sig}{INSTRUCTIONS}, defined as follows:

signature INSTRUCTIONS =
   structure C        : \href{cells.html}{CELLS}
   structure Constant : \href{constants.html}{CONSTANT}
   structure LabelExp : \href{labelexp.html}{LABELEXP}
      sharing LabelExp.Constant = Constant

   type operand   
   type ea         
   type addressing_mode
   type instruction 

Type \sml{operand} is used to represent ioperands,
\sml{ea} is used to represent effective addresses, type 
\sml{addressing_mode} is used to represent the internal addressing mode
used by the architecture.  Note that these are all abstract according to 
the signature, so the client has complete freedom in choosing the most
convenient representation for these things.

   For architectures that have full \newdef{predication}
built-in, such as the C6xx or IA-64, the instruction set should be
extended to satisfy the signature: 
signature \mlrischref{instructions/pred-instructions.sig}{PREDICATED_INSTRUCTIONS} =
   type predicate  
This basically says that the type that is used to represent a predicate
can be implemented however the client wants.  This flexibility
is quite important since the predication model may differ substantially
from architecture to architecture.

For example, in the TI C6, there are no seperate predicate register files
and integer registers double as predicate registers, and the predicate
true is any non-zero value.  Each instruction can be predicated under a
predicate register or its negation.  In contrasts, architectures such as
IA-64 and HP's Playdoh incorporate separate predicate registers into their 
architectures.  In Playdoh, \newdef{predicate defining} instructions 
actually set a pair of complementary predicate registers, 
and instructions can only
be predicated under the value of a predicate register, not its negation.

   VLIW architectures differ from superscalars in that
resource assignments are statically determined at compile time.
We distinguish between two different types of resources, namely
\newdef{functional units} and \newdef{data paths}.  
The latter type is particularly
important for clustered architectures.
The following signature
is used to describe VLIW instructions:
signature \mlrischref{instructions/vliw-instructions.sig}{VLIW\_INSTRUCTIONS} =

   structure FU : \mlrischref{instructions/funits.sig}{FUNITS}
   structure DP : \mlrischref{instructions/datapaths.sig}{DATAPATHS}
The signature \sml{FUNITS} is used to describe functional unit
resources, while the signature \sml{DATAPATHS} is used to describe
data paths.

\subsection{Predicated VLIW}

Finally, instructions sets for predicated VLIW/EPIC machines should match
the signature 
signature \mlrischref{instructions/pred-vliw-instructions.sig}{PREDICATED_VLIW_INSTRUCTIONS} =
   type predicate

ViewVC Help
Powered by ViewVC 1.0.0