From 03889c1a1e45d591d8d2568cff400de002777612 Mon Sep 17 00:00:00 2001
From: Joel Sherrill <joel.sherrill@OARcorp.com>
Date: Mon, 19 Oct 1998 21:46:32 +0000
Subject: All of the Supplemental manuals are now generated as automatically as
 possible.

---
 doc/supplements/m68k/callconv.t | 33 +--------------------------------
 1 file changed, 1 insertion(+), 32 deletions(-)

(limited to 'doc/supplements/m68k/callconv.t')

diff --git a/doc/supplements/m68k/callconv.t b/doc/supplements/m68k/callconv.t
index 014222a9fc..1ebdf7592e 100644
--- a/doc/supplements/m68k/callconv.t
+++ b/doc/supplements/m68k/callconv.t
@@ -6,24 +6,8 @@
 @c  $Id$
 @c
 
-@ifinfo
-@node Calling Conventions, Calling Conventions Introduction, CPU Model Dependent Features Extend Byte to Long Instruction, Top
-@end ifinfo
 @chapter Calling Conventions
-@ifinfo
-@menu
-* Calling Conventions Introduction::
-* Calling Conventions Processor Background::
-* 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 Processor Background, Calling Conventions, Calling Conventions
-@end ifinfo
+
 @section Introduction
 
 Each high-level language compiler generates
@@ -44,9 +28,6 @@ target processor are the same, different compilers may use
 different calling conventions.  As a result, calling conventions
 are both processor and compiler dependent.
 
-@ifinfo
-@node Calling Conventions Processor Background, Calling Conventions Calling Mechanism, Calling Conventions Introduction, Calling Conventions
-@end ifinfo
 @section Processor Background
 
 The MC68xxx architecture supports a simple yet
@@ -61,18 +42,12 @@ automatically save or restore any registers.  It is the
 responsibility of the high-level language compiler to define the
 register preservation and usage convention.
 
-@ifinfo
-@node Calling Conventions Calling Mechanism, Calling Conventions Register Usage, Calling Conventions Processor Background, Calling Conventions
-@end ifinfo
 @section Calling Mechanism
 
 All RTEMS directives are invoked using either a bsr
 or jsr instruction and return to the user application via the
 rts instruction.
 
-@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 bsr and jsr instructions do
@@ -82,9 +57,6 @@ not preserved by RTEMS directives therefore, the contents of
 these registers should not be assumed upon return from any RTEMS
 directive.
 
-@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 on the
@@ -112,9 +84,6 @@ from the stack after control is returned to the caller.  This
 removal is typically accomplished by adding the size of the
 argument list in bytes to the current stack pointer.
 
-@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
-- 
cgit v1.2.3