extend.texi, [...]: Eliminate overfull or underfull hboxes.

        * doc/extend.texi, doc/gcc.texi, doc/install-old.texi,
        doc/invoke.texi, doc/md.texi, doc/rtl.texi, doc/include/gpl.texi:
        Eliminate overfull or underfull hboxes.

From-SVN: r45012

gcc/ChangeLog

 2001-08-18  Zack Weinberg  <zackw@panix.com>
 
-	* cpperror.c: Use VA_OPEN/VA_CLOSE/VA_FIXEDARG throughout. 
+	* doc/extend.texi, doc/gcc.texi, doc/install-old.texi,
+	doc/invoke.texi, doc/md.texi, doc/rtl.texi, doc/include/gpl.texi:
+	Eliminate overfull or underfull hboxes.
+
+2001-08-18  Zack Weinberg  <zackw@panix.com>
+
+	* cpperror.c: Use VA_OPEN/VA_CLOSE/VA_FIXEDARG throughout.
 
 2001-08-18  Zack Weinberg  <zackw@panix.com>
 
@@ -12,12 +18,12 @@
 	TARGET_SCHED_ADJUST_PRIORITY, TARGET_SCHED_ISSUE_RATE,
 	TARGET_SCHED_VARIABLE_ISSUE, TARGET_SCHED_INIT,
 	TARGET_SCHED_FINISH, TARGET_SCHED_REORDER,
-	TARGET_SCHED_REORDER2, TARGET_SCHED_CYCLE_DISPLAY): 
+	TARGET_SCHED_REORDER2, TARGET_SCHED_CYCLE_DISPLAY):
 	New hook #defines to be overridden.
 	(TARGET_SCHED): Bring them all together.
 	(TARGET_INITIALIZER): Update.
 	* target.h: Don't forward declare struct rtx_def.  Use 'rtx'
-	instead of 'struct rtx_def *' throughout.  
+	instead of 'struct rtx_def *' throughout.
 	(struct sched): New set of hooks for the scheduler.
 	* Makefile.in (haifa-sched.o): Depend on target.h.
 	* doc/tm.texi: Document the new scheduler hooks, together in
@@ -81,7 +87,7 @@
 2001-08-18  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
 
 	* except.c (TYPE_HASH): Delete.
-	
+
 	* objc/objc-act.c (HASHFUNCTION): Cast to size_t, not
 	HOST_WIDE_INT.
 
@@ -140,7 +146,7 @@
 	(MAX_OFILE_ALIGNMENT): New.
 	(ASM_OUTPUT_ALIGNED_LOCAL): Use bss_section.
 	* config/mips/mips.c (mips_make_temp_file, temp_filename): Remove.
-	(copy_file_data): Split out from 
+	(copy_file_data): Split out from
 	(mips_asm_file_end): ... here.
 	(mips_asm_file_start): Remove extra .section directive.  Use
 	tmpfile instead of mips_make_temp_file.

gcc/doc/gcc.texi

@@ -2529,11 +2529,18 @@ our current development sources are available by CVS (see
 @uref{http://gcc.gnu.org/cvs.html}).  Source and binary snapshots are
 also available for FTP; see @uref{http://gcc.gnu.org/snapshots.html}.
 
-If you would like to work on improvements to GCC, please read
-@uref{http://gcc.gnu.org/contribute.html} and
-@uref{http://gcc.gnu.org/contributewhy.html} for information on how to
-make useful contributions and avoid duplication of effort.  Suggested
-projects are listed at @uref{http://gcc.gnu.org/projects/}.
+If you would like to work on improvements to GCC, please read the
+advice at these URLs:
+
+@smallexample
+@uref{http://gcc.gnu.org/contribute.html} 
+@uref{http://gcc.gnu.org/contributewhy.html}
+@end smallexample
+
+@noindent
+for information on how to make useful contributions and avoid
+duplication of effort.  Suggested projects are listed at
+@uref{http://gcc.gnu.org/projects/}.
 
 @node VMS
 @chapter Using GCC on VMS
@@ -3229,23 +3236,23 @@ tree node that represents an expression has a data type attached.
 Variables are represented as declaration nodes.
 
 The language-independent source files for parsing are
-@file{stor-layout.c}, @file{fold-const.c}, and @file{tree.c}.
+@file{tree.c}, @file{fold-const.c}, and @file{stor-layout.c}.
 There are also header files @file{tree.h} and @file{tree.def}
 which define the format of the tree representation.
 
-C Preprocessing, for language front ends, that want or require it, is
+C preprocessing, for language front ends, that want or require it, is
 performed by cpplib, which is covered in seperate documentation.  In
-particular, the internals are covered in @xref{Top, ,Cpplib internals, cppinternals, Cpplib Internals}.
-
+particular, the internals are covered in @xref{Top, ,Cpplib internals,
+cppinternals, Cpplib Internals}.
 
 @c Avoiding overfull is tricky here.
 The source files to parse C are
-@file{c-aux-info.c},
 @file{c-convert.c},
 @file{c-decl.c},
 @file{c-errors.c},
 @file{c-lang.c},
 @file{c-parse.in},
+@file{c-aux-info.c},
 and
 @file{c-typeck.c},
 along with a header file
@@ -3266,19 +3273,18 @@ They are @file{parse.y},
 @file{cp-tree.h}, and @file{decl.h}.
 
 The special source files for parsing Objective-C are in @file{objc/}.
-They are @file{objc-parse.y}, @file{objc-act.c}, @file{objc-tree.def}, and
-@file{objc-act.h}.  Certain C-specific files are used for this as
-well.
+They are @file{objc-act.c}, @file{objc-tree.def}, and @file{objc-act.h}.
+Certain C-specific files are used for this as well.
 
 The files
 @file{c-common.c},
 @file{c-common.def},
 @file{c-dump.c},
 @file{c-format.c},
-@file{c-lex.c},
 @file{c-pragma.c},
-and
 @file{c-semantics.c},
+and
+@file{c-lex.c},
 along with header files
 @file{c-common.h},
 @file{c-dump.h},
@@ -4193,7 +4199,9 @@ For example, in the PowerPC embedded ABI support, it is not desirable
 to build libraries compiled with the @option{-mcall-aix} option
 and either of the @option{-fleading-underscore} or @option{-mlittle} options
 at the same time.  Therefore @code{MULTILIB_EXCEPTIONS} is set to
-@code{*mcall-aix/*fleading-underscore* *mlittle/*mcall-aix*}.
+@smallexample
+*mcall-aix/*fleading-underscore* *mlittle/*mcall-aix*
+@end smallexample
 
 @findex MULTILIB_EXTRA_OPTS
 @item MULTILIB_EXTRA_OPTS

gcc/doc/include/gpl.texi

@@ -61,7 +61,7 @@ patent must be licensed for everyone's free use or not licensed at all.
 modification follow.
 
 @iftex
-@unnumberedsec TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+@unnumberedsec TERMS AND CONDITIONS FOR COPYING,@*DISTRIBUTION AND MODIFICATION
 @end iftex
 @ifnottex
 @center TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

gcc/doc/install-old.texi

@@ -430,11 +430,11 @@ machine, the cross-compiler can use them also.
 Otherwise, you're on your own in finding header files to use when
 cross-compiling.
 
-When you have found suitable header files, put them in the directory
-@file{/usr/local/@var{target}/include}, before building the cross
-compiler.  Then installation will run fixincludes properly and install
-the corrected versions of the header files where the compiler will use
-them.
+When you have found suitable header files, you should put them in the
+directory @file{/usr/local/@var{target}/include}, before building the
+cross compiler.  Then installation will run fixincludes properly and
+install the corrected versions of the header files where the compiler
+will use them.
 
 Provide the header files before you build the cross-compiler, because
 the build stage actually runs the cross-compiler to produce parts of
@@ -613,9 +613,9 @@ $ install replace sys$common:[syslib]dcltables
 @end smallexample
 
 @item
-Type @samp{@@make-gcc} to recompile everything (alternatively, submit
-the file @file{make-gcc.com} to a batch queue).  If you wish to build
-the GNU C++ compiler as well as the GNU CC compiler, you must first edit
+Type @samp{@@make-gcc} to recompile everything, or submit the file
+@file{make-gcc.com} to a batch queue.  If you wish to build the GNU C++
+compiler as well as the GNU CC compiler, you must first edit
 @file{make-gcc.com} and follow the instructions that appear in the
 comments.
 
@@ -680,12 +680,6 @@ the read-only bit set, and the linker will generate warning messages
 about mismatched psect attributes for these variables.  These warning
 messages are merely a nuisance, and can safely be ignored.
 
-If you are compiling with a version of GNU CC older than 1.33, specify
-@samp{/DEFINE=("inline=")} as an option in all the compilations.  This
-requires editing all the @code{gcc} commands in @file{make-cc1.com}.
-(The older versions had problems supporting @code{inline}.)  Once you
-have a working 1.33 or newer GNU CC, you can change this file back.
-
 @item
 If you want to build GNU CC with the VAX C compiler, you will need to
 make minor changes in @file{make-cccp.com} and @file{make-cc1.com}
@@ -829,11 +823,12 @@ done).
 is where @code{g++} looks first for header files.  The C++ library
 installs only target independent header files in that directory.
 
-@code{LOCAL_INCLUDE_DIR} is used only for a native compiler.  It is
-normally @file{/usr/local/include}.  GNU CC searches this directory so
-that users can install header files in @file{/usr/local/include}.
+@code{LOCAL_INCLUDE_DIR} is used only by native compilers.  GNU CC
+doesn't install anything there.  It is normally
+@file{/usr/local/include}.  This is where local additions to a packaged
+system should place header files.
 
-@code{CROSS_INCLUDE_DIR} is used only for a cross compiler.  GNU CC
+@code{CROSS_INCLUDE_DIR} is used only by cross compilers.  GNU CC
 doesn't install anything there.
 
 @code{TOOL_INCLUDE_DIR} is used for both native and cross compilers.  It

gcc/doc/md.texi

@@ -448,8 +448,6 @@ those listed in the @code{match_parallel}.
 A typical use of @code{match_parallel} is to match load and store
 multiple expressions, which can contain a variable number of elements
 in a @code{parallel}.  For example,
-@c the following is *still* going over.  need to change the code.
-@c also need to work on grouping of this example.  --mew 1feb93
 
 @smallexample
 (define_insn ""
@@ -463,7 +461,7 @@ in a @code{parallel}.  For example,
 @end smallexample
 
 This example comes from @file{a29k.md}.  The function
-@code{load_multiple_operations} is defined in @file{a29k.c} and checks
+@code{load_multiple_operation} is defined in @file{a29k.c} and checks
 that subsequent elements in the @code{parallel} are the same as the
 @code{set} in the pattern, except that they are referencing subsequent
 registers and memory locations.
@@ -1295,12 +1293,12 @@ general-purpose registers respectively; @pxref{Simple Constraints}), and
 @samp{I}, usually the letter indicating the most common
 immediate-constant format.
 
-For each machine architecture, the @file{config/@var{machine}.h} file
-defines additional constraints.  These constraints are used by the
-compiler itself for instruction generation, as well as for @code{asm}
-statements; therefore, some of the constraints are not particularly
-interesting for @code{asm}.  The constraints are defined through these
-macros:
+For each machine architecture, the
+@file{config/@var{machine}/@var{machine}.h} file defines additional
+constraints.  These constraints are used by the compiler itself for
+instruction generation, as well as for @code{asm} statements; therefore,
+some of the constraints are not particularly interesting for @code{asm}.
+The constraints are defined through these macros:
 
 @table @code
 @item REG_CLASS_FROM_LETTER
@@ -2068,9 +2066,8 @@ machines explicit memory references will get optional reloads.
 If a scratch register is required to move an object to or from memory,
 it can be allocated using @code{gen_reg_rtx} prior to life analysis.
 
-If there are cases needing
-scratch registers after reload, you must define
-@code{SECONDARY_INPUT_RELOAD_CLASS} and perhaps also
+If there are cases which need scratch registers during or after reload,
+you must define @code{SECONDARY_INPUT_RELOAD_CLASS} and/or
 @code{SECONDARY_OUTPUT_RELOAD_CLASS} to detect them, and provide
 patterns @samp{reload_in@var{m}} or @samp{reload_out@var{m}} to handle
 them.  @xref{Register Classes}.
@@ -2947,8 +2944,8 @@ the function should return.  This will normally need to copied by the
 pattern to some special register or memory location.
 
 This pattern only needs to be defined if call frame exception handling
-is to be used, and simple moves to @code{EH_RETURN_STACKADJ_RTX} and
-@code{EH_RETURN_HANDLER_RTX} are not sufficient.
+is to be used, and simple moves involving @code{EH_RETURN_STACKADJ_RTX}
+and @code{EH_RETURN_HANDLER_RTX} are not sufficient.
 
 @cindex @code{prologue} instruction pattern
 @anchor{prologue instruction pattern}
@@ -3251,9 +3248,9 @@ iterations.  This avoids the need for fetching and executing a
 @samp{dbra}-like instruction and avoids pipeline stalls associated with
 the jump.
 
-GCC has three special named patterns to support low overhead looping,
-@samp{decrement_and_branch_until_zero}, @samp{doloop_begin}, and
-@samp{doloop_end}.  The first pattern,
+GCC has three special named patterns to support low overhead looping.
+They are @samp{decrement_and_branch_until_zero}, @samp{doloop_begin},
+and @samp{doloop_end}.  The first pattern,
 @samp{decrement_and_branch_until_zero}, is not emitted during RTL
 generation but may be emitted during the instruction combination phase.
 This requires the assistance of the loop optimizer, using information
@@ -3888,7 +3885,8 @@ from i386.md:
   "TARGET_ZERO_EXTEND_WITH_AND && !optimize_size"
   "#"
   "&& reload_completed"
-  [(parallel [(set (match_dup 0) (and:SI (match_dup 0) (const_int 65535)))
+  [(parallel [(set (match_dup 0) 
+                   (and:SI (match_dup 0) (const_int 65535)))
 	      (clobber (reg:CC 17))])]
   ""
   [(set_attr "type" "alu1")])
@@ -4749,9 +4747,10 @@ as follows:
    return (get_attr_length (insn) == 4
            ? "b %l0" : "l r15,=a(%l0); br r15");
 @}
-  [(set (attr "length") (if_then_else (lt (match_dup 0) (const_int 4096))
-                                      (const_int 4)
-                                      (const_int 6)))])
+  [(set (attr "length")
+        (if_then_else (lt (match_dup 0) (const_int 4096))
+                      (const_int 4)
+                      (const_int 6)))])
 @end smallexample
 
 @node Constant Attributes

gcc/doc/rtl.texi

@@ -1527,8 +1527,8 @@ than the operands.  Write the pattern for this as
 where @var{m} is wider than the modes of @var{x} and @var{y}, which need
 not be the same.
 
-Write patterns for unsigned widening multiplication similarly using
-@code{zero_extend}.
+For unsigned widening multiplication, use the same idiom, but with
+@code{zero_extend} instead of @code{sign_extend}.
 
 @findex div
 @cindex division
@@ -2169,7 +2169,8 @@ either wrap around or use saturating addition depending on the value
 of a special control register:
 
 @example
-(parallel [(set (reg:SI 2) (unspec:SI [(reg:SI 3) (reg:SI 4)] 0))
+(parallel [(set (reg:SI 2) (unspec:SI [(reg:SI 3) 
+                                       (reg:SI 4)] 0))
            (use (reg:SI 1))])
 @end example