Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

PR gas/15212

Browse Source 
* doc/c-arc.texi (ARC Directives): Use @code instead of @bullte
	for table format.
	* doc/c-arm.texi (ARM-Instruction-Set): Likewise.  Also add text
	to the @item directives.
	(ARM-Neon-Alignment): Move to correct place in the document.
	* doc/c-cr16.texi (CR16 Operand Qualifiers): Fix up table
	formatting.
	* doc/c-tic54x.texi (TIC54X-Subsyms): Correct use of
	@smallexample.
This commit is contained in:
Nick Clifton
2013-03-14 10:00:46 +00:00
parent e2be70a0e1
commit ba724cfc0c
5 changed files with 76 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

61
gas/doc/c-arm.texi
View File

@@ -1,5 +1,4 @@
@c Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
@c 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
@c Copyright 1996-2013 Free Software Foundation, Inc.
@c This is part of the GAS manual.
@c For copying conditions, see the file as.texinfo.
@@ -390,29 +389,29 @@ ARM and THUMB instructions had their own, separate syntaxes. The new,
@code{unified} syntax, which can be selected via the @code{.syntax}
directive, and has the following main features:
@table @bullet
@item
@table @code
@item 1
Immediate operands do not require a @code{#} prefix.
@item
@item 2
The @code{IT} instruction may appear, and if it does it is validated
against subsequent conditional affixes. In ARM mode it does not
generate machine code, in THUMB mode it does.
@item
@item 3
For ARM instructions the conditional affixes always appear at the end
of the instruction. For THUMB instructions conditional affixes can be
used, but only inside the scope of an @code{IT} instruction.
@item
@item 4
All of the instructions new to the V6T2 architecture (and later) are
available. (Only a few such instructions can be written in the
@code{divided} syntax).
@item
@item 5
The @code{.N} and @code{.W} suffixes are recognized and honored.
@item
@item 6
All instructions set the flags if and only if they have an @code{s}
affix.
@end table
@@ -451,28 +450,6 @@ Either @samp{#} or @samp{$} can be used to indicate immediate operands.
@cindex register names, ARM
*TODO* Explain about ARM register naming, and the predefined names.
@node ARM-Neon-Alignment
@subsection NEON Alignment Specifiers
@cindex alignment for NEON instructions
Some NEON load/store instructions allow an optional address
alignment qualifier.
The ARM documentation specifies that this is indicated by
@samp{@@ @var{align}}. However GAS already interprets
the @samp{@@} character as a "line comment" start,
so @samp{: @var{align}} is used instead. For example:
@smallexample
vld1.8 @{q0@}, [r0, :128]
@end smallexample
@node ARM Floating Point
@section Floating Point
@cindex floating point, ARM (@sc{ieee})
@cindex ARM floating point (@sc{ieee})
The ARM family uses @sc{ieee} floating-point numbers.
@node ARM-Relocations
@subsection ARM relocation generation
@@ -519,6 +496,28 @@ respectively. For example to load the 32-bit address of foo into r0:
MOVT r0, #:upper16:foo
@end smallexample
@node ARM-Neon-Alignment
@subsection NEON Alignment Specifiers
@cindex alignment for NEON instructions
Some NEON load/store instructions allow an optional address
alignment qualifier.
The ARM documentation specifies that this is indicated by
@samp{@@ @var{align}}. However GAS already interprets
the @samp{@@} character as a "line comment" start,
so @samp{: @var{align}} is used instead. For example:
@smallexample
vld1.8 @{q0@}, [r0, :128]
@end smallexample
@node ARM Floating Point
@section Floating Point
@cindex floating point, ARM (@sc{ieee})
@cindex ARM floating point (@sc{ieee})
The ARM family uses @sc{ieee} floating-point numbers.
@node ARM Directives
@section ARM Machine Directives