Renamed a lot and got as much as possible automatically generated.

1 files changed, 1 insertions, 52 deletions

diff --git a/doc/supplements/powerpc/callconv.t b/doc/supplements/powerpc/callconv.t
index 1bf2c8fc79..7fc4bfd60f 100644
--- a/doc/supplements/powerpc/callconv.t
+++ b/doc/supplements/powerpc/callconv.t
@@ -6,25 +6,8 @@
 @c  $Id$
 @c
 
-@ifinfo
-@node Calling Conventions, Calling Conventions Introduction, CPU Model Dependent Features Low Power Model, Top
-@end ifinfo
 @chapter Calling Conventions
-@ifinfo
-@menu
-* Calling Conventions Introduction::
-* Calling Conventions Programming Model::
-* Calling Conventions Call and Return Mechanism::
-* Calling Conventions Calling Mechanism::
-* Calling Conventions Register Usage::
-* Calling Conventions Parameter Passing::
-* Calling Conventions User-Provided Routines::
-@end menu
-@end ifinfo
-
-@ifinfo
-@node Calling Conventions Introduction, Calling Conventions Programming Model, Calling Conventions, Calling Conventions
-@end ifinfo
+
 @section Introduction
 
 Each high-level language compiler generates
@@ -51,24 +34,11 @@ RTEMS supports the Embedded Application Binary Interface (EABI)
 calling convention.  Documentation for EABI is available by sending
 a message with a subject line of "EABI" to eabi@@goth.sis.mot.com.
 
-@ifinfo
-@node Calling Conventions Programming Model, Calling Conventions Non-Floating Point Registers, Calling Conventions Introduction, Calling Conventions
-@end ifinfo
 @section Programming Model
-@ifinfo
-@menu
-* Calling Conventions Non-Floating Point Registers::
-* Calling Conventions Floating Point Registers::
-* Calling Conventions Special Registers::
-@end menu
-@end ifinfo
 
 This section discusses the programming model for the
 PowerPC architecture.
 
-@ifinfo
-@node Calling Conventions Non-Floating Point Registers, Calling Conventions Floating Point Registers, Calling Conventions Programming Model, Calling Conventions Programming Model
-@end ifinfo
 @subsection Non-Floating Point Registers
 
 The PowerPC architecture defines thirty-two non-floating point registers
@@ -149,9 +119,6 @@ The following table describes the role of each of these registers:
 @end ifset
 
 
-@ifinfo
-@node Calling Conventions Floating Point Registers, Calling Conventions Special Registers, Calling Conventions Non-Floating Point Registers, Calling Conventions Programming Model
-@end ifinfo
 @subsection Floating Point Registers
 
 The PowerPC architecture includes thirty-two, sixty-four bit
@@ -164,9 +131,6 @@ and the type of result generated by floating-point operations.
 Additionally, it controls the rounding mode of operations and allows the
 reporting of floating exceptions to be enabled or disabled.
 
-@ifinfo
-@node Calling Conventions Special Registers, Calling Conventions Call and Return Mechanism, Calling Conventions Floating Point Registers, Calling Conventions Programming Model
-@end ifinfo
 @subsection Special Registers
 
 The PowerPC architecture includes a number of special registers
@@ -195,9 +159,6 @@ for indirect function calls and jumps.
 
 @end table
 
-@ifinfo
-@node Calling Conventions Call and Return Mechanism, Calling Conventions Calling Mechanism, Calling Conventions Special Registers, Calling Conventions
-@end ifinfo
 @section Call and Return Mechanism
 
 The PowerPC architecture supports a simple yet effective call
@@ -225,18 +186,12 @@ The LR may be accessed as special purpose register 8 (@code{SPR8}) using the
 "move from special register" (@code{mfspr}) and
 "move to special register" (@code{mtspr}) instructions.
 
-@ifinfo
-@node Calling Conventions Calling Mechanism, Calling Conventions Register Usage, Calling Conventions Call and Return Mechanism, Calling Conventions
-@end ifinfo
 @section Calling Mechanism
 
 All RTEMS directives are invoked using the regular
 PowerPC EABI calling convention via the @code{bl} or
 @code{bla} instructions.
 
-@ifinfo
-@node Calling Conventions Register Usage, Calling Conventions Parameter Passing, Calling Conventions Calling Mechanism, Calling Conventions
-@end ifinfo
 @section Register Usage
 
 As discussed above, the call instruction does not
@@ -246,9 +201,6 @@ across subroutine calls.  The callee is responsible for saving
 callee-preserved registers to the program stack and restoring them
 before returning to the caller.
 
-@ifinfo
-@node Calling Conventions Parameter Passing, Calling Conventions User-Provided Routines, Calling Conventions Register Usage, Calling Conventions
-@end ifinfo
 @section Parameter Passing
 
 RTEMS assumes that arguments are placed in the
@@ -268,9 +220,6 @@ load first argument into r3
 invoke directive
 @end example
 
-@ifinfo
-@node Calling Conventions User-Provided Routines, Memory Model, Calling Conventions Parameter Passing, Calling Conventions
-@end ifinfo
 @section User-Provided Routines
 
 All user-provided routines invoked by RTEMS, such as