Makefile.in (TEXI_GCCINT_FILES): Add libgcc.texi.

2003-03-15  Aldy Hernandez <aldyh@redhat.com>
	    Zack Weinberg  <zack@codesourcery.com>

	* Makefile.in (TEXI_GCCINT_FILES): Add libgcc.texi.
	* doc/libgcc.texi: New file.
	* doc/interface.texi: Delete paragraph about libgcc interface.
	* doc/gccint.texi: Add libgcc menu entry and @include libgcc.texi.

From-SVN: r64416

gcc/ChangeLog

+2003-03-15  Aldy Hernandez <aldyh@redhat.com>
+	    Zack Weinberg  <zack@codesourcery.com>
+
+	* Makefile.in (TEXI_GCCINT_FILES): Add libgcc.texi.
+	* doc/libgcc.texi: New file.
+	* doc/interface.texi: Delete paragraph about libgcc interface.
+	* doc/gccint.texi: Add libgcc menu entry and @include libgcc.texi.
+
 2003-03-15  Jason Merrill  <jason@redhat.com>
 
 	PR debug/9039

gcc/doc/gccint.texi

@@ -140,6 +140,7 @@ Additional tutorial information is linked to from
 * Contributing::    How to contribute to testing and developing GCC.
 * Portability::     Goals of GCC's portability features.
 * Interface::       Function-call interface of GCC output.
+* Libgcc::          Low-level runtime library used by GCC.
 * Languages::       Languages for which GCC front ends are written.
 * Source Tree::     GCC source tree structure and build system.
 * Passes::          Order of passes, what they do, and what each file is for.
@@ -168,6 +169,7 @@ Additional tutorial information is linked to from
 @include contribute.texi
 @include portability.texi
 @include interface.texi
+@include libgcc.texi
 @include languages.texi
 @include sourcebuild.texi
 @include passes.texi

gcc/doc/interface.texi

@@ -83,20 +83,3 @@ go in a register:
   @dots{}
 @}
 @end example
-
-@cindex arithmetic libraries
-@cindex math libraries
-@opindex msoft-float
-Code compiled with GCC may call certain library routines.  Most of
-them handle arithmetic for which there are no instructions.  This
-includes multiply and divide on some machines, and floating point
-operations on any machine for which floating point support is disabled
-with @option{-msoft-float}.  Some standard parts of the C library, such as
-@code{bcopy} or @code{memcpy}, are also called automatically.  The usual
-function call interface is used for calling the library routines.
-
-Some of these routines can be defined in mostly machine-independent C;
-they appear in @file{libgcc2.c}.  Others must be hand-written in
-assembly language for each processor.  Wherever they are defined, they
-are compiled into the support library, @file{libgcc.a}, which is
-automatically searched when you link programs with GCC@.