source: rtems/doc/supplements/i960/cpumodel.t @ ae68ff0

4.104.114.84.95
Last change on this file since ae68ff0 was ae68ff0, checked in by Joel Sherrill <joel.sherrill@…>, on 05/27/97 at 12:40:11

Initial revision

  • Property mode set to 100644
File size: 3.3 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-1997.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6
7@ifinfo
8@node CPU Model Dependent Features, CPU Model Dependent Features Introduction, Preface, Top
9@end ifinfo
10@chapter CPU Model Dependent Features
11@ifinfo
12@menu
13* CPU Model Dependent Features Introduction::
14* CPU Model Dependent Features CPU Model Name::
15* CPU Model Dependent Features Floating Point Unit::
16@end menu
17@end ifinfo
18
19@ifinfo
20@node CPU Model Dependent Features Introduction, CPU Model Dependent Features CPU Model Name, CPU Model Dependent Features, CPU Model Dependent Features
21@end ifinfo
22@section Introduction
23
24Microprocessors are generally classified into
25families with a variety of CPU models or implementations within
26that family.  Within a processor family, there is a high level
27of binary compatibility.  This family may be based on either an
28architectural specification or on maintaining compatibility with
29a popular processor.  Recent microprocessor families such as the
30SPARC or PA-RISC are based on an architectural specification
31which is independent or any particular CPU model or
32implementation.  Older families such as the M68xxx and the iX86
33evolved as the manufacturer strived to produce higher
34performance processor models which maintained binary
35compatibility with older models.
36
37RTEMS takes advantage of the similarity of the
38various models within a CPU family.  Although the models do vary
39in significant ways, the high level of compatibility makes it
40possible to share the bulk of the CPU dependent executive code
41across the entire family.  Each processor family supported by
42RTEMS has a list of features which vary between CPU models
43within a family.  For example, the most common model dependent
44feature regardless of CPU family is the presence or absence of a
45floating point unit or coprocessor.  When defining the list of
46features present on a particular CPU model, one simply notes
47that floating point hardware is or is not present and defines a
48single constant appropriately.  Conditional compilation is
49utilized to include the appropriate source code for this CPU
50model's feature set.  It is important to note that this means
51that RTEMS is thus compiled using the appropriate feature set
52and compilation flags optimal for this CPU model used.  The
53alternative would be to generate a binary which would execute on
54all family members using only the features which were always
55present.
56
57This chapter presents the set of features which vary
58across i960 implementations and are of importance to RTEMS.
59The set of CPU model feature macros are defined in the file
60c/src/exec/score/cpu/i960/i960.h based upon the particular CPU
61model defined on the compilation command line.
62
63@ifinfo
64@node CPU Model Dependent Features CPU Model Name, CPU Model Dependent Features Floating Point Unit, CPU Model Dependent Features Introduction, CPU Model Dependent Features
65@end ifinfo
66@section CPU Model Name
67
68The macro CPU_MODEL_NAME is a string which designates
69the name of this CPU model.  For example, for the Intel i960CA,
70this macro is set to the string "i960ca".
71
72@ifinfo
73@node CPU Model Dependent Features Floating Point Unit, Calling Conventions, CPU Model Dependent Features CPU Model Name, CPU Model Dependent Features
74@end ifinfo
75@section Floating Point Unit
76
77The macro I960_HAS_FPU is set to 1 to indicate that
78this CPU model has a hardware floating point unit and 0
79otherwise.
Note: See TracBrowser for help on using the repository browser.