This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Trailing whitespace removal patch for manual


This patch removes trailing whitespace (again) from the manuals in
gcc/doc.  It passes "make info" and "make dvi".  Applied to mainline.

Should trailing whitespace in general be removed from the whole source
tree (except for the cpp testsuite)?

Index: ChangeLog
===================================================================
RCS file: /cvs/gcc/gcc/gcc/ChangeLog,v
retrieving revision 1.13136
diff -u -r1.13136 ChangeLog
--- ChangeLog	2002/02/23 08:56:19	1.13136
+++ ChangeLog	2002/02/23 12:56:28
@@ -1,3 +1,9 @@
+2002-02-23  Joseph S. Myers  <jsm28@cam.ac.uk>
+
+	* doc/contribute.texi, doc/extend.texi, doc/install.texi,
+	doc/invoke.texi, doc/md.texi, doc/passes.texi, doc/rtl.texi,
+	doc/standards.texi, doc/tm.texi: Remove trailing whitespace.
+
 2002-02-23  Jakub Jelinek  <jakub@redhat.com>
 
 	PR optimization/5747
Index: doc/contribute.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/contribute.texi,v
retrieving revision 1.1
diff -u -r1.1 contribute.texi
--- contribute.texi	2001/11/11 11:31:24	1.1
+++ contribute.texi	2002/02/23 12:56:28
@@ -15,7 +15,7 @@
 advice at these URLs:
 
 @smallexample
-@uref{http://gcc.gnu.org/contribute.html} 
+@uref{http://gcc.gnu.org/contribute.html}
 @uref{http://gcc.gnu.org/contributewhy.html}
 @end smallexample
 
Index: doc/extend.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/extend.texi,v
retrieving revision 1.63
diff -u -r1.63 extend.texi
--- extend.texi	2002/02/22 00:09:01	1.63
+++ extend.texi	2002/02/23 12:56:29
@@ -2556,7 +2556,7 @@
 than a function definition.  At present, such attribute specifiers apply
 to the declared object or function, but in future they may attach to the
 outermost adjacent declarator.  In simple cases there is no difference,
-but, for example, in 
+but, for example, in
 
 @smallexample
 void (****f)(void) __attribute__((noreturn));
@@ -2615,7 +2615,7 @@
 @var{type-qualifier-and-attribute-specifier-list} @var{Type}'' for
 @var{ident}.
 
-For example, 
+For example,
 
 @smallexample
 void (__attribute__((noreturn)) ****f) (void);
@@ -4634,7 +4634,7 @@
   @}
 @end smallexample
 
-Data prefetch does not generate faults if @var{addr} is invalid, but 
+Data prefetch does not generate faults if @var{addr} is invalid, but
 the address expression itself must be valid.  For example, a prefetch
 of @code{p->next} will not fault if @code{p->next} is not a valid
 address, but evaluation will fault if @code{p} is not a valid address.
@@ -5713,7 +5713,7 @@
 vector signed int vec_all_gt (vector signed char, vector signed char);
 vector signed int vec_all_gt (vector signed short,
                               vector unsigned short);
-vector signed int vec_all_gt (vector unsigned short,    
+vector signed int vec_all_gt (vector unsigned short,
                               vector signed short);
 vector signed int vec_all_gt (vector unsigned short,
                               vector unsigned short);
Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.91
diff -u -r1.91 install.texi
--- install.texi	2002/02/01 18:42:37	1.91
+++ install.texi	2002/02/23 12:56:29
@@ -615,7 +615,7 @@
 
 @item powerpc*-*-*, rs6000*-*-*
 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
-sysv, aix. 
+sysv, aix.
 
 @end table
 
@@ -863,7 +863,7 @@
 runtime libraries.
 
 We @strong{highly} recommend that GCC be built using GNU make;
-other versions may work, then again they might not.  
+other versions may work, then again they might not.
 GNU make is required for compiling GNAT, the Ada compiler.
 
 (For example, many broken versions of make will fail if you use the
@@ -921,7 +921,7 @@
 @item
 Build target tools for use by the compiler such as binutils (bfd,
 binutils, gas, gprof, ld, and opcodes)
-if they have been individually linked 
+if they have been individually linked
 or moved into the top level GCC source tree before configuring.
 
 @item
@@ -1050,7 +1050,7 @@
 @end example
 
 At the moment, the GNAT library and several tools for GNAT are not built
-by @samp{make bootstrap}.  You have to invoke 
+by @samp{make bootstrap}.  You have to invoke
 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
 subdirectory before proceeding with the next steps.
 
@@ -1059,10 +1059,10 @@
 
 @example
     cd @var{objdir}
-    @var{srcdir}/configure --enable-languages=c,ada 
+    @var{srcdir}/configure --enable-languages=c,ada
     cd @var{srcdir}/gcc/ada
     touch treeprs.ads [es]info.h nmake.ad[bs]
-    cd @var{objdir}    
+    cd @var{objdir}
     make bootstrap
     cd gcc
     make gnatlib_and_tools
@@ -2167,7 +2167,7 @@
 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
 
 GCC 3.0 supports HP-UX 11.  You must use GNU binutils 2.11 or above on
-this platform.  Thread support is not currently implemented for this 
+this platform.  Thread support is not currently implemented for this
 platform, so @option{--enable-threads} does not work.
 See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
 and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}.
@@ -2777,7 +2777,7 @@
 You absolutely @strong{must} use GNU sed and GNU make on this platform.
 
 
-On NeXTSTEP 3.x where x < 3 the build of GCC will abort during  
+On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
 stage1 with an error message like this:
 
 @example
@@ -3082,10 +3082,10 @@
 optimization option, you also need to use @option{-Olimit 3000}.
 
 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
-or later, 
+or later,
 and use the @option{--with-gnu-as} configure option when configuring GCC.
 GNU @command{as} is distributed as part of the binutils package.
-When using release 2.11.2, you need to apply a patch 
+When using release 2.11.2, you need to apply a patch
 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
 which will be included in the next release of binutils.
 
@@ -3360,14 +3360,14 @@
 <hr>
 @end html
 @heading @anchor{s390-*-linux*}s390-*-linux*
-S/390 system running Linux for S/390@. 
+S/390 system running Linux for S/390@.
 
 @html
 </p>
 <hr>
 @end html
 @heading @anchor{s390x-*-linux*}s390x-*-linux*
-zSeries system (64 Bit) running Linux for zSeries@. 
+zSeries system (64 Bit) running Linux for zSeries@.
 
 @html
 </p>
@@ -3488,7 +3488,7 @@
 only a partial fix for bug 4210064, but Sun doesn't know whether the
 partial fix is adequate for GCC@.  Revision -08 or later should fix
 the bug.  The current (as of 2001-09-24) revision is -14, and is included in
-the Solaris 7 Recommended Patch Cluster. 
+the Solaris 7 Recommended Patch Cluster.
 @end itemize
 
 
@@ -3685,7 +3685,7 @@
 shared objects and the GNU C library (glibc).  It also generates
 position-independent code (PIC) regardless of whether the
 @option{-fpic} or @option{-fPIC} options are used.  In other
-respects, this target is the same as the 
+respects, this target is the same as the
 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
 
 @html
Index: doc/invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.116
diff -u -r1.116 invoke.texi
--- invoke.texi	2002/02/20 07:24:10	1.116
+++ invoke.texi	2002/02/23 12:56:30
@@ -2586,7 +2586,7 @@
 @item -Wno-deprecated-declarations
 @opindex Wno-deprecated-declarations
 Do not warn about uses of functions, variables, and types marked as
-deprecated by using the @code{deprecated} attribute. 
+deprecated by using the @code{deprecated} attribute.
 (@pxref{Function Attributes}, @pxref{Variable Attributes},
 @pxref{Type Attributes}.)
 
@@ -8319,7 +8319,7 @@
 @opindex mexplicit-relocs
 @opindex mno-explicit-relocs
 Older Alpha assemblers provided no way to generate symbol relocations
-except via assembler macros.  Use of these macros does not allow 
+except via assembler macros.  Use of these macros does not allow
 optimial instruction scheduling.  GNU binutils as of version 2.12
 supports a new syntax that allows the compiler to explicitly mark
 which relocations should apply to which instructions.  This option
@@ -8330,7 +8330,7 @@
 @itemx -mlarge-data
 @opindex msmall-data
 @opindex mlarge-data
-When @option{-mexplicit-relocs} is in effect, static data is 
+When @option{-mexplicit-relocs} is in effect, static data is
 accessed via @dfn{gp-relative} relocations.  When @option{-msmall-data}
 is used, objects 8 bytes long or smaller are placed in a @dfn{small data area}
 (the @code{.sdata} and @code{.sbss} sections) and are accessed via
@@ -9321,7 +9321,7 @@
 @itemx -mno-backchain
 @opindex mbackchain
 @opindex mno-backchain
-Generate (or do not generate) code which maintains an explicit 
+Generate (or do not generate) code which maintains an explicit
 backchain within the stack frame that points to the caller's frame.
 This is currently needed to allow debugging.  The default is to
 generate the backchain.
@@ -9330,8 +9330,8 @@
 @itemx -mno-small-exec
 @opindex msmall-exec
 @opindex mno-small-exec
-Generate (or do not generate) code using the @code{bras} instruction 
-to do subroutine calls. 
+Generate (or do not generate) code using the @code{bras} instruction
+to do subroutine calls.
 This only works reliably if the total executable size does not
 exceed 64k.  The default is to use the @code{basr} instruction instead,
 which does not have this limitation.
@@ -9344,14 +9344,14 @@
 Linux for S/390 ABI@.  When @option{-m64} is specified, generate
 code compliant to the Linux for zSeries ABI@.  This allows GCC in
 particular to generate 64-bit instructions.  For the @samp{s390}
-targets, the default is @option{-m31}, while the @samp{s390x} 
+targets, the default is @option{-m31}, while the @samp{s390x}
 targets default to @option{-m64}.
 
 @item -mmvcle
 @itemx -mno-mvcle
 @opindex mmvcle
 @opindex mno-mvcle
-Generate (or do not generate) code using the @code{mvcle} instruction 
+Generate (or do not generate) code using the @code{mvcle} instruction
 to perform block moves.  When @option{-mno-mvcle} is specifed,
 use a @code{mvc} loop instead.  This is the default.
 
Index: doc/md.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/md.texi,v
retrieving revision 1.34
diff -u -r1.34 md.texi
--- md.texi	2002/01/23 21:03:51	1.34
+++ md.texi	2002/02/23 12:56:31
@@ -185,10 +185,10 @@
         (match_operand:SI 0 "general_operand" "rm"))]
   ""
   "*
-@{ 
+@{
   if (TARGET_68020 || ! ADDRESS_REG_P (operands[0]))
     return \"tstl %0\";
-  return \"cmpl #0,%0\"; 
+  return \"cmpl #0,%0\";
 @}")
 @end example
 
@@ -200,10 +200,10 @@
   [(set (cc0)
         (match_operand:SI 0 "general_operand" "rm"))]
   ""
-@{ 
+@{
   if (TARGET_68020 || ! ADDRESS_REG_P (operands[0]))
     return "tstl %0";
-  return "cmpl #0,%0"; 
+  return "cmpl #0,%0";
 @})
 @end example
 
@@ -2208,7 +2208,7 @@
 macro in @pxref{Register Classes}.
 
 There are special restrictions on the form of the @code{match_operand}s
-used in these patterns.  First, only the predicate for the reload 
+used in these patterns.  First, only the predicate for the reload
 operand is examined, i.e., @code{reload_in} examines operand 1, but not
 the predicates for operand 0 or 2.  Second, there may be only one
 alternative in the constraints.  Third, only a single register class
@@ -3955,7 +3955,7 @@
 The splitter is allowed to split jump instructions into sequence of
 jumps or create new jumps in while splitting non-jump instructions.  As
 the central flowgraph and branch prediction information needs to be updated,
-several restriction apply. 
+several restriction apply.
 
 Splitting of jump instruction into sequence that over by another jump
 instruction is always valid, as compiler expect identical behavior of new
@@ -4004,7 +4004,7 @@
   "TARGET_ZERO_EXTEND_WITH_AND && !optimize_size"
   "#"
   "&& reload_completed"
-  [(parallel [(set (match_dup 0) 
+  [(parallel [(set (match_dup 0)
                    (and:SI (match_dup 0) (const_int 65535)))
 	      (clobber (reg:CC 17))])]
   ""
@@ -4041,7 +4041,7 @@
 
 @smallexample
 
-(include "filestuff") 
+(include "filestuff")
 
 @end smallexample
 
@@ -4050,14 +4050,14 @@
 directory @file{gcc/config/target} is regarded as the default directory.
 
 
-Machine descriptions may be split up into smaller more manageable subsections 
-and placed into subdirectories. 
+Machine descriptions may be split up into smaller more manageable subsections
+and placed into subdirectories.
 
 By specifying:
 
 @smallexample
 
-(include "BOGUS/filestuff") 
+(include "BOGUS/filestuff")
 
 @end smallexample
 
@@ -4066,10 +4066,10 @@
 Specifying an absolute path for the include file such as;
 @smallexample
 
-(include "/u2/BOGUS/filestuff") 
+(include "/u2/BOGUS/filestuff")
 
 @end smallexample
-is permitted but is not encouraged. 
+is permitted but is not encouraged.
 
 @subsection RTL Generation Tool Options for Directory Search
 @cindex directory options .md
Index: doc/passes.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/passes.texi,v
retrieving revision 1.6
diff -u -r1.6 passes.texi
--- passes.texi	2001/12/21 16:19:14	1.6
+++ passes.texi	2002/02/23 12:56:31
@@ -130,7 +130,7 @@
 @cindex inline on trees, automatic
 Currently, the main optimization performed here is tree-based
 inlining.
-This is implemented in @file{tree-inline.c} and used by both C and C++.  
+This is implemented in @file{tree-inline.c} and used by both C and C++.
 Note that tree based inlining turns off rtx based inlining (since it's more
 powerful, it would be a waste of time to do rtx based inlining in
 addition).
Index: doc/rtl.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/rtl.texi,v
retrieving revision 1.29
diff -u -r1.29 rtl.texi
--- rtl.texi	2002/02/19 17:27:12	1.29
+++ rtl.texi	2002/02/23 12:56:31
@@ -2317,7 +2317,7 @@
 of a special control register:
 
 @example
-(parallel [(set (reg:SI 2) (unspec:SI [(reg:SI 3) 
+(parallel [(set (reg:SI 2) (unspec:SI [(reg:SI 3)
                                        (reg:SI 4)] 0))
            (use (reg:SI 1))])
 @end example
Index: doc/standards.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/standards.texi,v
retrieving revision 1.2
diff -u -r1.2 standards.texi
--- standards.texi	2001/11/12 23:35:22	1.2
+++ standards.texi	2002/02/23 12:56:31
@@ -164,7 +164,7 @@
 is an older example.  @uref{http://www.gnustep.org} includes useful
 information as well.
 
-@xref{Top, GNAT Reference Manual, About This Guide, gnat_rm, 
+@xref{Top, GNAT Reference Manual, About This Guide, gnat_rm,
 GNAT Reference Manual}, for information on standard
 conformance and compatibility of the Ada compiler.
 
Index: doc/tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.101
diff -u -r1.101 tm.texi
--- tm.texi	2002/02/17 14:55:10	1.101
+++ tm.texi	2002/02/23 12:56:32
@@ -1604,10 +1604,10 @@
 @findex TARGET_VTABLE_USES_DESCRIPTORS
 @item TARGET_VTABLE_USES_DESCRIPTORS
 Normally, the C++ compiler uses function pointers in vtables.  This
-macro allows the target to change to use ``function descriptors'' 
+macro allows the target to change to use ``function descriptors''
 instead.  Function descriptors are found on targets for whom a
 function pointer is actually a small data structure.  Normally the
-data structure consists of the actual code address plus a data 
+data structure consists of the actual code address plus a data
 pointer to which the function's data is relative.
 
 If vtables are used, the value of this macro should be the number
@@ -1729,10 +1729,10 @@
 @cindex call-used register
 @cindex call-clobbered register
 @cindex call-saved register
-Like @code{CALL_USED_REGISTERS} except this macro doesn't require 
-that the entire set of @code{FIXED_REGISTERS} be included.  
+Like @code{CALL_USED_REGISTERS} except this macro doesn't require
+that the entire set of @code{FIXED_REGISTERS} be included.
 (@code{CALL_USED_REGISTERS} must be a superset of @code{FIXED_REGISTERS}).
-This macro is optional.  If not specified, it defaults to the value 
+This macro is optional.  If not specified, it defaults to the value
 of @code{CALL_USED_REGISTERS}.
 
 @findex HARD_REGNO_CALL_PART_CLOBBERED
@@ -2805,7 +2805,7 @@
 for the address of the code being executed and @code{context->cfa} for
 the stack pointer value.  If the frame can be decoded, the register save
 addresses should be updated in @var{fs} and the macro should branch to
-@var{success}.  If the frame cannot be decoded, the macro should do 
+@var{success}.  If the frame cannot be decoded, the macro should do
 nothing.
 @end table
 
@@ -5770,7 +5770,7 @@
 should have attributes as specified by @var{flags}, which is a bit mask
 of the @code{SECTION_*} flags defined in @file{output.h}.  If @var{align}
 is nonzero, it contains an alignment in bytes to be used for the section,
-otherwise some target default should be used.  Only targets that must 
+otherwise some target default should be used.  Only targets that must
 specify an alignment within the section directive need pay attention to
 @var{align} -- we will still use @code{ASM_OUTPUT_ALIGN}.
 @end deftypefn
@@ -6481,7 +6481,7 @@
 
 This method will be chosen as the default by @file{target-def.h} if
 @code{TARGET_ASM_NAMED_SECTION} is defined.  A target that does not
-support arbitrary sections, but does support special designated 
+support arbitrary sections, but does support special designated
 constructor and destructor sections may define @code{CTORS_SECTION_ASM_OP}
 and @code{DTORS_SECTION_ASM_OP} to achieve the same effect.
 
@@ -6591,7 +6591,7 @@
 function called @code{_GLOBAL__DI} will be generated.
 
 This function and the following one are used by collect2 when linking a
-shared library that needs constructors or destructors, or has DWARF2 
+shared library that needs constructors or destructors, or has DWARF2
 exception tables embedded in the code.
 
 @item COLLECT_SHARED_FINI_FUNC (@var{stream}, @var{func})
@@ -6872,7 +6872,7 @@
 
 If this macro is defined, you may use constructs of the form
 @smallexample
-@samp{@{option0|option1|option2@dots{}@}} 
+@samp{@{option0|option1|option2@dots{}@}}
 @end smallexample
 @noindent
 in the output templates of patterns (@pxref{Output Template}) or in the

-- 
Joseph S. Myers
jsm28@cam.ac.uk


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]