FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
supported on all architectures.
This commit is contained in:
Mark Mitchell 2006-04-16 18:15:55 +00:00
parent ffdc4eeddf
commit 58ab4f3d64
2 changed files with 18 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gas/ChangeLog
View file

@ -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

17
gas/doc/as.texinfo
View file

@ -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