* doc/as.texinfo: Mention that some .type syntaxes are not

	supported on all architectures.

diff --git a/ChangeLog.csl b/ChangeLog.csl
index ad80d950f0179eb6a7fed697ba6c56f0a23bbbb2..77390c526a9036e30e2917d96237e0b3e796e0ee 100644 (file)
--- a/ChangeLog.csl
+++ b/ChangeLog.csl
@@ -1,3 +1,8 @@
+2006-04-28  Mark Mitchell  <mark@codesourcery.com>
+
+       * doc/as.texinfo: Mention that some .type syntaxes are not
+       supported on all architectures.
+
 2006-04-27  Richard Sandiford  <richard@codesourcery.com>
 
        include/opcodes/

diff --git a/gas/doc/as.texinfo b/gas/doc/as.texinfo
index 4fe0ef4ca8d2c345f3f92559a548b49c7b78fc26..b71b0d1ef0fbc7241de871f3a4a21bca1de43c72 100644 (file)
--- a/gas/doc/as.texinfo
+++ b/gas/doc/as.texinfo
@@ -5964,7 +5964,15 @@ For ELF targets, the @code{.type} directive is used like this:
 This sets the type of symbol @var{name} to be either a
 function symbol or an object symbol.  There are five different syntaxes
 supported for the @var{type description} field, in order to provide
-compatibility with various other assemblers.  The syntaxes supported are:
+compatibility with various other assemblers.  
+
+Because some of the characters used in these syntaxes (such as @samp{@@} and
+@samp{#}) are comment characters for some architectures, some of the syntaxes
+below do not work on all architectures.  The first variant will be accepted by
+the assembler on all architectures, so that syntax should be used if you
+require maximum portability.
+
+The syntaxes supported are:
 
 @smallexample
   .type <name>,#function