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

	supported on all architectures.

diff --git a/gas/ChangeLog b/gas/ChangeLog
index e7425364fbbae14162f00b0f8d1c16f19dbb5498..00ec913b6372db9edab432a6d6aba85ca5cd69d8 100644 (file)
--- a/gas/ChangeLog
+++ b/gas/ChangeLog
@@ -1,3 +1,8 @@
+2006-04-16  Mark Mitchell  <mark@codesourcery.com>
+
+       * doc/as.texinfo: Mention that some .type syntaxes are not
+       supported on all architectures.
+
 2006-04-14  Sterling Augustine  <sterling@tensilica.com>
 
        * config/tc-xtensa.c (emit_single_op): Do not relax MOVI

diff --git a/gas/doc/as.texinfo b/gas/doc/as.texinfo
index 4fe0ef4ca8d2c345f3f92559a548b49c7b78fc26..dfe786075cf9635ae9ce4751725c9f6f14c1405b 100644 (file)
--- a/gas/doc/as.texinfo
+++ b/gas/doc/as.texinfo
@@ -5964,9 +5964,21 @@ 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 GNU assembler on all architectures so that variant should be used for
+maximum portability, if you do not need to assemble your code with other
+assemblers.
+
+The syntaxes supported are:
 
 @smallexample
+  .type <name> STT_FUNCTION
+  .type <name> STT_OBJECT
+
   .type <name>,#function
   .type <name>,#object
 
@@ -5978,9 +5990,6 @@ compatibility with various other assemblers.  The syntaxes supported are:
   
   .type <name>,"function"
   .type <name>,"object"
-  
-  .type <name> STT_FUNCTION
-  .type <name> STT_OBJECT
 @end smallexample
 @end ifset
 @end ifset