rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-15 14:37:22 +08:00
Code Issues Packages Projects Releases Wiki Activity

powerpc, sparc, sparc64: Correct tables

Browse Source
This commit is contained in:
Joel Sherrill 2016-10-28 13:07:04 -05:00
parent 23a5ce4498
commit 0c978901d0
3 changed files with 57 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
cpu_supplement/powerpc.rst
View File

@ -373,14 +373,14 @@ architecture does not require the processor to generate alignment exceptions.
The following table lists the alignment requirements for a variety of data The following table lists the alignment requirements for a variety of data
accesses: accesses:
+--------------+-----------------------+ ============== ======================
| Data Type | Alignment Requirement | Data Type Alignment Requirement
+--------------+-----------------------+ ============== ======================
| byte | 1 | byte 1
| half-word | 2 | half-word 2
| word | 4 | word 4
| doubleword | 8 | doubleword 8
+--------------+-----------------------+ ============== ======================
Doubleword load and store operations are only available in PowerPC CPU models Doubleword load and store operations are only available in PowerPC CPU models
which are sixty-four bit implementations. which are sixty-four bit implementations.

55
cpu_supplement/sparc.rst
View File

@ -236,34 +236,27 @@ architecturally defined role in the programming model which provides an
alternate name. The following table describes the mapping between the 32 alternate name. The following table describes the mapping between the 32
registers and the register sets: registers and the register sets:
+-----------------+----------------+------------------+ ================ ================ ===================
| Register Number | Register Names | Description | Register Number Register Names Description
+-----------------+----------------+------------------+ ================ ================ ===================
| 0 - 7 | g0 - g7 | Global Registers | 0 - 7 g0 - g7 Global Registers
+-----------------+----------------+------------------+ 8 - 15 o0 - o7 Output Registers
| 8 - 15 | o0 - o7 | Output Registers | 16 - 23 l0 - l7 Local Registers
+-----------------+----------------+------------------+ 24 - 31 i0 - i7 Input Registers
| 16 - 23 | l0 - l7 | Local Registers | ================ ================ ===================
+-----------------+----------------+------------------+
| 24 - 31 | i0 - i7 | Input Registers |
+-----------------+----------------+------------------+
As mentioned above, some of the registers serve defined roles in the As mentioned above, some of the registers serve defined roles in the
programming model. The following table describes the role of each of these programming model. The following table describes the role of each of these
registers: registers:
+---------------+----------------+----------------------+ ============== ================ ==================================
| Register Name | Alternate Name | Description | Register Name Alternate Name Description
+---------------+----------------+----------------------+ ============== ================ ==================================
| g0 | na | reads return 0 | g0 na reads return 0, writes are ignored
| | | writes are ignored | o6 sp stack pointer
+---------------+----------------+----------------------+ i6 fp frame pointer
| o6 | sp | stack pointer | i7 na return address
+---------------+----------------+----------------------+ ============== ================ ==================================
| i6 | fp | frame pointer |
+---------------+----------------+----------------------+
| i7 | na | return address |
+---------------+----------------+----------------------+
The registers g2 through g4 are reserved for applications. GCC uses them as The registers g2 through g4 are reserved for applications. GCC uses them as
volatile registers by default. So they are treated like volatile registers in volatile registers by default. So they are treated like volatile registers in
@ -483,14 +476,14 @@ endian fashion by the SPARC. Memory accesses which are not properly aligned
generate a "memory address not aligned" trap (type number 7). The following generate a "memory address not aligned" trap (type number 7). The following
table lists the alignment requirements for a variety of data accesses: table lists the alignment requirements for a variety of data accesses:
+--------------+-----------------------+ ============== ======================
| Data Type | Alignment Requirement | Data Type Alignment Requirement
+--------------+-----------------------+ ============== ======================
| byte | 1 | byte 1
| half-word | 2 | half-word 2
| word | 4 | word 4
| doubleword | 8 | doubleword 8
+--------------+-----------------------+ ============== ======================
Doubleword load and store operations must use a pair of registers as their Doubleword load and store operations must use a pair of registers as their
source or destination. This pair of registers must be an adjacent pair of source or destination. This pair of registers must be an adjacent pair of

59
cpu_supplement/sparc64.rst
View File

@ -143,34 +143,27 @@ architecturally defined role in the programming model which provides an
alternate name. The following table describes the mapping between the 32 alternate name. The following table describes the mapping between the 32
registers and the register sets: registers and the register sets:
+-----------------+----------------+------------------+ ================ ================ ===================
| Register Number | Register Names | Description | Register Number Register Names Description
+-----------------+----------------+------------------+ ================ ================ ===================
| 0 - 7 | g0 - g7 | Global Registers | 0 - 7 g0 - g7 Global Registers
+-----------------+----------------+------------------+ 8 - 15 o0 - o7 Output Registers
| 8 - 15 | o0 - o7 | Output Registers | 16 - 23 l0 - l7 Local Registers
+-----------------+----------------+------------------+ 24 - 31 i0 - i7 Input Registers
| 16 - 23 | l0 - l7 | Local Registers | ================ ================ ===================
+-----------------+----------------+------------------+
| 24 - 31 | i0 - i7 | Input Registers |
+-----------------+----------------+------------------+
As mentioned above, some of the registers serve defined roles in the As mentioned above, some of the registers serve defined roles in the
programming model. The following table describes the role of each of these programming model. The following table describes the role of each of these
registers: registers:
+---------------+----------------+----------------------+ ============== ================ ==================================
| Register Name | Alternate Name | Description | Register Name Alternate Name Description
+---------------+----------------+----------------------+ ============== ================ ==================================
| g0 | na | reads return 0 | g0 na reads return 0, writes are ignored
| | | writes are ignored | o6 sp stack pointer
+---------------+----------------+----------------------+ i6 fp frame pointer
| o6 | sp | stack pointer | i7 na return address
+---------------+----------------+----------------------+ ============== ================ ==================================
| i6 | fp | frame pointer |
+---------------+----------------+----------------------+
| i7 | na | return address |
+---------------+----------------+----------------------+
Floating Point Registers Floating Point Registers
~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
@ -384,17 +377,15 @@ fashion by the SPARC. Memory accesses which are not properly aligned generate a
"memory address not aligned" trap (type number 0x34). The following table lists "memory address not aligned" trap (type number 0x34). The following table lists
the alignment requirements for a variety of data accesses: the alignment requirements for a variety of data accesses:
.. table:: ============== ======================
Data Type Alignment Requirement
+--------------+-----------------------+ ============== ======================
| Data Type | Alignment Requirement | byte 1
+--------------+-----------------------+ half-word 2
| byte | 1 | word 4
| half-word | 2 | doubleword 8
| word | 4 | quadword 16
| doubleword | 8 | ============== ======================
| quadword | 16 |
+--------------+-----------------------+
RTEMS currently does not support any SPARC Memory Management Units, therefore, RTEMS currently does not support any SPARC Memory Management Units, therefore,
virtual memory or segmentation systems involving the SPARC are not supported. virtual memory or segmentation systems involving the SPARC are not supported.