Since d10v is public now, remove all sanitization statements

2 files changed, 49 insertions, 56 deletions

diff --git a/gas/doc/.Sanitize b/gas/doc/.Sanitize
index 8770cc7..0ffaa20 100644
--- a/gas/doc/.Sanitize
+++ b/gas/doc/.Sanitize
@@ -94,34 +94,6 @@ if [ -n "${verbose}" ] ; then
 	echo Processing \"arc\"...
 fi
 
-d10v_files="all.texi as.texinfo"
-if ( echo $* | grep keep\-d10v > /dev/null ) ; then
-	for i in $d10v_files ; do
-		if test ! -d $i && (grep sanitize-d10v $i > /dev/null) ; then
-			if [ -n "${verbose}" ] ; then
-				echo Keeping d10v stuff in $i
-			fi
-		fi
-	done
-else
-	for i in $d10v_files ; do
-		if test ! -d $i && (grep sanitize-d10v $i > /dev/null) ; then
-			if [ -n "${verbose}" ] ; then
-				echo Removing traces of \"d10v\" from $i...
-			fi
-			cp $i new
-			sed '/start\-sanitize\-d10v/,/end-\sanitize\-d10v/d' < $i > new
-			if [ -n "${safe}" -a ! -f .Recover/$i ] ; then
-				if [ -n "${verbose}" ] ; then
-					echo Caching $i in .Recover...
-				fi
-				mv $i .Recover
-			fi
-			mv new $i
-		fi
-	done
-fi
-
 for i in * ; do
 	if test ! -d $i && (grep sanitize $i > /dev/null) ; then
 		echo '***' Some mentions of Sanitize are still left in $i! 1>&2
diff --git a/gas/doc/as.texinfo b/gas/doc/as.texinfo
index 3e962ce..864229a 100644
--- a/gas/doc/as.texinfo
+++ b/gas/doc/as.texinfo
@@ -207,11 +207,9 @@ Here is a brief summary of how to invoke @code{@value{AS}}.  For details,
  [ -mbig-endian | -mlittle-endian ]
 @end ifset
 @c end-sanitize-arc
-@c start-sanitize-d10v
 @ifset D10V
  [ -O ]
 @end ifset
-@c end-sanitize-d10v
 
 @ifset H8
 @c Hitachi family chips have no machine-dependent assembler options
@@ -221,7 +219,7 @@ Here is a brief summary of how to invoke @code{@value{AS}}.  For details,
 @end ifset
 @ifset SPARC
 @c The order here is important.  See c-sparc.texi.
- [ -Av6 | -Av7 | -Av8 | -Asparclite | -Av9 | -Av9a ]
+ [ -Av6 | -Av7 | -Av8 | -Asparclet | -Asparclite | -Av9 | -Av9a ]
  [ -xarch=v8plus | -xarch=v8plusa ] [ -bump ]
 @end ifset
 @ifset Z8000
@@ -359,7 +357,6 @@ Generate ``little endian'' format output.
 @end table
 @end ifset
 
-@c start-sanitize-d10v
 @ifset D10V
 The following options are available when @value{AS} is configured for
 a D10V processor.
@@ -370,7 +367,6 @@ a D10V processor.
 Optimize output by parallelizing instructions.
 @end table
 @end ifset
-@c end-sanitize-d10v
 
 @ifset I960
 The following options are available when @value{AS} is configured for the
@@ -423,7 +419,7 @@ The following options are available when @code{@value{AS}} is configured
 for the SPARC architecture:
 
 @table @code
-@item -Av6 | -Av7 | -Av8 | -Asparclite | -Av9 | -Av9a
+@item -Av6 | -Av7 | -Av8 | -Asparclet | -Asparclite | -Av9 | -Av9a
 Explicitly select a variant of the SPARC architecture.
 
 @item -xarch=v8plus | -xarch=v8plusa
@@ -3014,18 +3010,27 @@ but ignores it.
 @end ifset
 
 @node Align
-@section @code{.align @var{abs-expr} , @var{abs-expr}}
+@section @code{.align @var{abs-expr}, @var{abs-expr}, @var{abs-expr}}
 
 @cindex padding the location counter
 @cindex @code{align} directive
-Pad the location counter (in the current subsection) to a particular
-storage boundary.  The first expression (which must be absolute) is the
-alignment required, as described below.
-The second expression (also absolute) gives the value to be stored in
-the padding bytes.  It (and the comma) may be omitted.  If it is
-omitted, the padding bytes are zero.  
-For the alpha, if the section is marked as containing code and the
-padding expression is omitted, then the space is filled with no-ops.
+Pad the location counter (in the current subsection) to a particular storage
+boundary.  The first expression (which must be absolute) is the alignment
+required, as described below.
+
+The second expression (also absolute) gives the fill value to be stored in the
+padding bytes.  It (and the comma) may be omitted.  If it is omitted, the
+padding bytes are normally zero.  However, on some systems, if the section is
+marked as containing code and the fill value is omitted, the space is filled
+with no-op instructions.
+
+The third expression is also absolute, and is also optional.  If it is present,
+it is the maximum number of bytes that should be skipped by this alignment
+directive.  If doing the alignment would require skipping more bytes than the
+specified maximum, then the alignment is not done at all.  You can omit the
+fill value (the second argument) entirely by simply using two commas after the
+required alignment; this can be useful if you want the alignment to be filled
+with no-op instructions when appropriate.
 
 The way the required alignment is specified varies from system to system.
 For the a29k, hppa, m68k, m88k, w65, sparc, and Hitachi SH, and i386 using ELF
@@ -3084,7 +3089,7 @@ trailing zero byte) into consecutive addresses.
 a zero byte.  The ``z'' in @samp{.asciz} stands for ``zero''.
 
 @node Balign
-@section @code{.balign[wl] @var{abs-expr} , @var{abs-expr}}
+@section @code{.balign[wl] @var{abs-expr}, @var{abs-expr}, @var{abs-expr}}
 
 @cindex padding the location counter given number of bytes
 @cindex @code{balign} directive
@@ -3094,9 +3099,19 @@ alignment request in bytes.  For example @samp{.balign 8} advances
 the location counter until it is a multiple of 8.  If the location counter
 is already a multiple of 8, no change is needed.
 
-The second expression (also absolute) gives the value to be stored in
-the padding bytes.  It (and the comma) may be omitted.  If it is
-omitted, the padding bytes are zero.
+The second expression (also absolute) gives the fill value to be stored in the
+padding bytes.  It (and the comma) may be omitted.  If it is omitted, the
+padding bytes are normally zero.  However, on some systems, if the section is
+marked as containing code and the fill value is omitted, the space is filled
+with no-op instructions.
+
+The third expression is also absolute, and is also optional.  If it is present,
+it is the maximum number of bytes that should be skipped by this alignment
+directive.  If doing the alignment would require skipping more bytes than the
+specified maximum, then the alignment is not done at all.  You can omit the
+fill value (the second argument) entirely by simply using two commas after the
+required alignment; this can be useful if you want the alignment to be filled
+with no-op instructions when appropriate.
 
 @cindex @code{balignw} directive
 @cindex @code{balignl} directive
@@ -3858,7 +3873,7 @@ absolute expression.  If the comma and @var{fill} are omitted,
 @var{fill} defaults to zero.
 
 @node P2align
-@section @code{.p2align[wl] @var{abs-expr} , @var{abs-expr}}
+@section @code{.p2align[wl] @var{abs-expr}, @var{abs-expr}, @var{abs-expr}}
 
 @cindex padding the location counter given a power of two
 @cindex @code{p2align} directive
@@ -3869,9 +3884,19 @@ advancement.  For example @samp{.p2align 3} advances the location
 counter until it a multiple of 8.  If the location counter is already a
 multiple of 8, no change is needed.
 
-The second expression (also absolute) gives the value to be stored in
-the padding bytes.  It (and the comma) may be omitted.  If it is
-omitted, the padding bytes are zero.
+The second expression (also absolute) gives the fill value to be stored in the
+padding bytes.  It (and the comma) may be omitted.  If it is omitted, the
+padding bytes are normally zero.  However, on some systems, if the section is
+marked as containing code and the fill value is omitted, the space is filled
+with no-op instructions.
+
+The third expression is also absolute, and is also optional.  If it is present,
+it is the maximum number of bytes that should be skipped by this alignment
+directive.  If doing the alignment would require skipping more bytes than the
+specified maximum, then the alignment is not done at all.  You can omit the
+fill value (the second argument) entirely by simply using two commas after the
+required alignment; this can be useful if you want the alignment to be filled
+with no-op instructions when appropriate.
 
 @cindex @code{p2alignw} directive
 @cindex @code{p2alignl} directive
@@ -4077,7 +4102,7 @@ section is executable
 Set the value of @var{symbol} to @var{expression}.  This
 changes @var{symbol}'s value and type to conform to
 @var{expression}.  If @var{symbol} was flagged as external, it remains
-flagged. (@xref{Symbol Attributes}.)
+flagged (@pxref{Symbol Attributes}).
 
 You may @code{.set} a symbol many times in the same assembly.
 
@@ -4446,11 +4471,9 @@ subject, see the hardware manufacturer's manual.
 * ARC-Dependent::               ARC Dependent Features
 @end ifset
 @c end-sanitize-arc
-@c start-sanitize-d10v
 @ifset D10V
 * D10V-Dependent::              D10V Dependent Features
 @end ifset
-@c end-sanitize-d10v
 @ifset H8/300
 * H8/300-Dependent::            Hitachi H8/300 Dependent Features
 @end ifset
@@ -4597,11 +4620,9 @@ family.
 @end ifclear
 @end ifset
 
-@c start-sanitize-d10v
 @ifset D10V
 @include c-d10v.texi
 @end ifset
-@c end-sanitize-d10v
 
 @ifset H8/300
 @include c-h8300.texi