source: rtems/doc/supplements/hppa1_1/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.0 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@end menu
18@end ifinfo
19
20@ifinfo
21@node CPU Model Dependent Features Introduction, CPU Model Dependent Features CPU Model Name, CPU Model Dependent Features, CPU Model Dependent Features
22@end ifinfo
23@section Introduction
24
25Microprocessors are generally classified into
26families with a variety of CPU models or implementations within
27that family.  Within a processor family, there is a high level
28of binary compatibility.  This family may be based on either an
29architectural specification or on maintaining compatibility with
30a popular processor.  Recent microprocessor families such as the
31SPARC or PA-RISC are based on an architectural specification
32which is independent or any particular CPU model or
33implementation.  Older families such as the M68xxx and the iX86
34evolved as the manufacturer strived to produce higher
35performance processor models which maintained binary
36compatibility with older models.
37
38RTEMS takes advantage of the similarity of the
39various models within a CPU family.  Although the models do vary
40in significant ways, the high level of compatibility makes it
41possible to share the bulk of the CPU dependent executive code
42across the entire family.  Each processor family supported by
43RTEMS has a list of features which vary between CPU models
44within a family.  For example, the most common model dependent
45feature regardless of CPU family is the presence or absence of a
46floating point unit or coprocessor.  When defining the list of
47features present on a particular CPU model, one simply notes
48that floating point hardware is or is not present and defines a
49single constant appropriately.  Conditional compilation is
50utilized to include the appropriate source code for this CPU
51model's feature set.  It is important to note that this means
52that RTEMS is thus compiled using the appropriate feature set
53and compilation flags optimal for this CPU model used.  The
54alternative would be to generate a binary which would execute on
55all family members using only the features which were always
56present.
57
58This chapter presents the set of features which vary
59across PA-RISC implementations and are of importance to RTEMS.
60The set of CPU model feature macros are defined in the file
61c/src/exec/score/cpu/hppa1_1/hppa.h based upon the particular CPU
62model defined on the compilation command line.
63
64@ifinfo
65@node CPU Model Dependent Features CPU Model Name, Calling Conventions, CPU Model Dependent Features Introduction, CPU Model Dependent Features
66@end ifinfo
67@section CPU Model Name
68
69The macro CPU_MODEL_NAME is a string which designates
70the name of this CPU model.  For example, for the Hewlett Packard
71PA-7100 CPU model, this macro is set to the string "hppa 7100".
Note: See TracBrowser for help on using the repository browser.