source: rtems/doc/supplements/i960/cpumodel.texi @ 1e524995

4.104.114.84.95
Last change on this file since 1e524995 was 1e524995, checked in by Joel Sherrill <joel.sherrill@…>, on 02/06/98 at 14:14:30

Updated copyrights

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