From: Mark Mitchell Date: Sat, 29 Apr 2006 00:33:35 +0000 (+0000) Subject: * doc/as.texinfo: Mention that some .type syntaxes are not X-Git-Tag: binutils-csl-morpho-4_1-4~1 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f79add9eb7a386eedce0427553f44238fc3d737c;p=thirdparty%2Fbinutils-gdb.git * doc/as.texinfo: Mention that some .type syntaxes are not supported on all architectures. --- diff --git a/ChangeLog.csl b/ChangeLog.csl index ad80d950f01..77390c526a9 100644 --- a/ChangeLog.csl +++ b/ChangeLog.csl @@ -1,3 +1,8 @@ +2006-04-28 Mark Mitchell + + * doc/as.texinfo: Mention that some .type syntaxes are not + supported on all architectures. + 2006-04-27 Richard Sandiford include/opcodes/ diff --git a/gas/doc/as.texinfo b/gas/doc/as.texinfo index 4fe0ef4ca8d..b71b0d1ef0f 100644 --- 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 ,#function