* config/tc-arm.c (arm_archs): Change "armv6" to "armv6j".
[deliverable/binutils-gdb.git] / gas / doc / c-arm.texi
1 @c Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2003
2 @c Free Software Foundation, Inc.
3 @c This is part of the GAS manual.
4 @c For copying conditions, see the file as.texinfo.
5
6 @ifset GENERIC
7 @page
8 @node ARM-Dependent
9 @chapter ARM Dependent Features
10 @end ifset
11
12 @ifclear GENERIC
13 @node Machine Dependencies
14 @chapter ARM Dependent Features
15 @end ifclear
16
17 @cindex ARM support
18 @cindex Thumb support
19 @menu
20 * ARM Options:: Options
21 * ARM Syntax:: Syntax
22 * ARM Floating Point:: Floating Point
23 * ARM Directives:: ARM Machine Directives
24 * ARM Opcodes:: Opcodes
25 * ARM Mapping Symbols:: Mapping Symbols
26 @end menu
27
28 @node ARM Options
29 @section Options
30 @cindex ARM options (none)
31 @cindex options for ARM (none)
32
33 @table @code
34
35 @cindex @code{-mcpu=} command line option, ARM
36 @item -mcpu=@var{processor}[+@var{extension}@dots{}]
37 This option specifies the target processor. The assembler will issue an
38 error message if an attempt is made to assemble an instruction which
39 will not execute on the target processor. The following processor names are
40 recognized:
41 @code{arm1},
42 @code{arm2},
43 @code{arm250},
44 @code{arm3},
45 @code{arm6},
46 @code{arm60},
47 @code{arm600},
48 @code{arm610},
49 @code{arm620},
50 @code{arm7},
51 @code{arm7m},
52 @code{arm7d},
53 @code{arm7dm},
54 @code{arm7di},
55 @code{arm7dmi},
56 @code{arm70},
57 @code{arm700},
58 @code{arm700i},
59 @code{arm710},
60 @code{arm710t},
61 @code{arm720},
62 @code{arm720t},
63 @code{arm740t},
64 @code{arm710c},
65 @code{arm7100},
66 @code{arm7500},
67 @code{arm7500fe},
68 @code{arm7t},
69 @code{arm7tdmi},
70 @code{arm8},
71 @code{arm810},
72 @code{strongarm},
73 @code{strongarm1},
74 @code{strongarm110},
75 @code{strongarm1100},
76 @code{strongarm1110},
77 @code{arm9},
78 @code{arm920},
79 @code{arm920t},
80 @code{arm922t},
81 @code{arm940t},
82 @code{arm9tdmi},
83 @code{arm9e},
84 @code{arm946e-r0},
85 @code{arm946e},
86 @code{arm966e-r0},
87 @code{arm966e},
88 @code{arm10t},
89 @code{arm10e},
90 @code{arm1020},
91 @code{arm1020t},
92 @code{arm1020e},
93 @code{arm1136js},
94 @code{arm1136jfs},
95 @code{ep9312} (ARM920 with Cirrus Maverick coprocessor),
96 @code{i80200} (Intel XScale processor)
97 @code{iwmmxt} (Intel(r) XScale processor with Wireless MMX(tm) technology coprocessor)
98 and
99 @code{xscale}.
100 The special name @code{all} may be used to allow the
101 assembler to accept instructions valid for any ARM processor.
102
103 In addition to the basic instruction set, the assembler can be told to
104 accept various extension mnemonics that extend the processor using the
105 co-processor instruction space. For example, @code{-mcpu=arm920+maverick}
106 is equivalent to specifying @code{-mcpu=ep9312}. The following extensions
107 are currently supported:
108 @code{+maverick}
109 @code{+iwmmxt}
110 and
111 @code{+xscale}.
112
113 @cindex @code{-march=} command line option, ARM
114 @item -march=@var{architecture}[+@var{extension}@dots{}]
115 This option specifies the target architecture. The assembler will issue
116 an error message if an attempt is made to assemble an instruction which
117 will not execute on the target architecture. The following architecture
118 names are recognized:
119 @code{armv1},
120 @code{armv2},
121 @code{armv2a},
122 @code{armv2s},
123 @code{armv3},
124 @code{armv3m},
125 @code{armv4},
126 @code{armv4xm},
127 @code{armv4t},
128 @code{armv4txm},
129 @code{armv5},
130 @code{armv5t},
131 @code{armv5txm},
132 @code{armv5te},
133 @code{armv5texp},
134 @code{armv6j},
135 @code{iwmmxt}
136 and
137 @code{xscale}.
138 If both @code{-mcpu} and
139 @code{-march} are specified, the assembler will use
140 the setting for @code{-mcpu}.
141
142 The architecture option can be extended with the same instruction set
143 extension options as the @code{-mcpu} option.
144
145 @cindex @code{-mfpu=} command line option, ARM
146 @item -mfpu=@var{floating-point-format}
147
148 This option specifies the floating point format to assemble for. The
149 assembler will issue an error message if an attempt is made to assemble
150 an instruction which will not execute on the target floating point unit.
151 The following format options are recognized:
152 @code{softfpa},
153 @code{fpe},
154 @code{fpe2},
155 @code{fpe3},
156 @code{fpa},
157 @code{fpa10},
158 @code{fpa11},
159 @code{arm7500fe},
160 @code{softvfp},
161 @code{softvfp+vfp},
162 @code{vfp},
163 @code{vfp10},
164 @code{vfp10-r0},
165 @code{vfp9},
166 @code{vfpxd},
167 @code{arm1020t},
168 @code{arm1020e},
169 @code{arm1136jfs}
170 and
171 @code{maverick}.
172
173 In addition to determining which instructions are assembled, this option
174 also affects the way in which the @code{.double} assembler directive behaves
175 when assembling little-endian code.
176
177 The default is dependent on the processor selected. For Architecture 5 or
178 later, the default is to assembler for VFP instructions; for earlier
179 architectures the default is to assemble for FPA instructions.
180
181 @cindex @code{-mthumb} command line option, ARM
182 @item -mthumb
183 This option specifies that the assembler should start assembling Thumb
184 instructions; that is, it should behave as though the file starts with a
185 @code{.code 16} directive.
186
187 @cindex @code{-mthumb-interwork} command line option, ARM
188 @item -mthumb-interwork
189 This option specifies that the output generated by the assembler should
190 be marked as supporting interworking.
191
192 @cindex @code{-mapcs} command line option, ARM
193 @item -mapcs @code{[26|32]}
194 This option specifies that the output generated by the assembler should
195 be marked as supporting the indicated version of the Arm Procedure.
196 Calling Standard.
197
198 @cindex @code{-matpcs} command line option, ARM
199 @item -matpcs
200 This option specifies that the output generated by the assembler should
201 be marked as supporting the Arm/Thumb Procedure Calling Standard. If
202 enabled this option will cause the assembler to create an empty
203 debugging section in the object file called .arm.atpcs. Debuggers can
204 use this to determine the ABI being used by.
205
206 @cindex @code{-mapcs-float} command line option, ARM
207 @item -mapcs-float
208 This indicates the floating point variant of the APCS should be
209 used. In this variant floating point arguments are passed in FP
210 registers rather than integer registers.
211
212 @cindex @code{-mapcs-reentrant} command line option, ARM
213 @item -mapcs-reentrant
214 This indicates that the reentrant variant of the APCS should be used.
215 This variant supports position independent code.
216
217 @cindex @code{-mfloat-abi=} command line option, ARM
218 @item -mfloat-abi=@var{abi}
219 This option specifies that the output generated by the assembler should be
220 marked as using specified floating point ABI.
221 The following values are recognized:
222 @code{soft},
223 @code{softfp}
224 and
225 @code{hard}.
226
227 @cindex @code{-EB} command line option, ARM
228 @item -EB
229 This option specifies that the output generated by the assembler should
230 be marked as being encoded for a big-endian processor.
231
232 @cindex @code{-EL} command line option, ARM
233 @item -EL
234 This option specifies that the output generated by the assembler should
235 be marked as being encoded for a little-endian processor.
236
237 @cindex @code{-k} command line option, ARM
238 @cindex PIC code generation for ARM
239 @item -k
240 This option specifies that the output of the assembler should be marked
241 as position-independent code (PIC).
242
243 @cindex @code{-moabi} command line option, ARM
244 @item -moabi
245 This indicates that the code should be assembled using the old ARM ELF
246 conventions, based on a beta release release of the ARM-ELF
247 specifications, rather than the default conventions which are based on
248 the final release of the ARM-ELF specifications.
249
250 @end table
251
252
253 @node ARM Syntax
254 @section Syntax
255 @menu
256 * ARM-Chars:: Special Characters
257 * ARM-Regs:: Register Names
258 @end menu
259
260 @node ARM-Chars
261 @subsection Special Characters
262
263 @cindex line comment character, ARM
264 @cindex ARM line comment character
265 The presence of a @samp{@@} on a line indicates the start of a comment
266 that extends to the end of the current line. If a @samp{#} appears as
267 the first character of a line, the whole line is treated as a comment.
268
269 @cindex line separator, ARM
270 @cindex statement separator, ARM
271 @cindex ARM line separator
272 The @samp{;} character can be used instead of a newline to separate
273 statements.
274
275 @cindex immediate character, ARM
276 @cindex ARM immediate character
277 Either @samp{#} or @samp{$} can be used to indicate immediate operands.
278
279 @cindex identifiers, ARM
280 @cindex ARM identifiers
281 *TODO* Explain about /data modifier on symbols.
282
283 @node ARM-Regs
284 @subsection Register Names
285
286 @cindex ARM register names
287 @cindex register names, ARM
288 *TODO* Explain about ARM register naming, and the predefined names.
289
290 @node ARM Floating Point
291 @section Floating Point
292
293 @cindex floating point, ARM (@sc{ieee})
294 @cindex ARM floating point (@sc{ieee})
295 The ARM family uses @sc{ieee} floating-point numbers.
296
297
298
299 @node ARM Directives
300 @section ARM Machine Directives
301
302 @cindex machine directives, ARM
303 @cindex ARM machine directives
304 @table @code
305
306 @cindex @code{align} directive, ARM
307 @item .align @var{expression} [, @var{expression}]
308 This is the generic @var{.align} directive. For the ARM however if the
309 first argument is zero (ie no alignment is needed) the assembler will
310 behave as if the argument had been 2 (ie pad to the next four byte
311 boundary). This is for compatibility with ARM's own assembler.
312
313 @cindex @code{req} directive, ARM
314 @item @var{name} .req @var{register name}
315 This creates an alias for @var{register name} called @var{name}. For
316 example:
317
318 @smallexample
319 foo .req r0
320 @end smallexample
321
322 @cindex @code{unreq} directive, ARM
323 @item .unreq @var{alias-name}
324 This undefines a register alias which was previously defined using the
325 @code{req} directive. For example:
326
327 @smallexample
328 foo .req r0
329 .unreq foo
330 @end smallexample
331
332 An error occurs if the name is undefined. Note - this pseudo op can
333 be used to delete builtin in register name aliases (eg 'r0'). This
334 should only be done if it is really necessary.
335
336 @cindex @code{code} directive, ARM
337 @item .code @code{[16|32]}
338 This directive selects the instruction set being generated. The value 16
339 selects Thumb, with the value 32 selecting ARM.
340
341 @cindex @code{thumb} directive, ARM
342 @item .thumb
343 This performs the same action as @var{.code 16}.
344
345 @cindex @code{arm} directive, ARM
346 @item .arm
347 This performs the same action as @var{.code 32}.
348
349 @cindex @code{force_thumb} directive, ARM
350 @item .force_thumb
351 This directive forces the selection of Thumb instructions, even if the
352 target processor does not support those instructions
353
354 @cindex @code{thumb_func} directive, ARM
355 @item .thumb_func
356 This directive specifies that the following symbol is the name of a
357 Thumb encoded function. This information is necessary in order to allow
358 the assembler and linker to generate correct code for interworking
359 between Arm and Thumb instructions and should be used even if
360 interworking is not going to be performed. The presence of this
361 directive also implies @code{.thumb}
362
363 @cindex @code{thumb_set} directive, ARM
364 @item .thumb_set
365 This performs the equivalent of a @code{.set} directive in that it
366 creates a symbol which is an alias for another symbol (possibly not yet
367 defined). This directive also has the added property in that it marks
368 the aliased symbol as being a thumb function entry point, in the same
369 way that the @code{.thumb_func} directive does.
370
371 @cindex @code{.ltorg} directive, ARM
372 @item .ltorg
373 This directive causes the current contents of the literal pool to be
374 dumped into the current section (which is assumed to be the .text
375 section) at the current location (aligned to a word boundary).
376 @code{GAS} maintains a separate literal pool for each section and each
377 sub-section. The @code{.ltorg} directive will only affect the literal
378 pool of the current section and sub-section. At the end of assembly
379 all remaining, un-empty literal pools will automatically be dumped.
380
381 Note - older versions of @code{GAS} would dump the current literal
382 pool any time a section change occurred. This is no longer done, since
383 it prevents accurate control of the placement of literal pools.
384
385 @cindex @code{.pool} directive, ARM
386 @item .pool
387 This is a synonym for .ltorg.
388
389 @end table
390
391 @node ARM Opcodes
392 @section Opcodes
393
394 @cindex ARM opcodes
395 @cindex opcodes for ARM
396 @code{@value{AS}} implements all the standard ARM opcodes. It also
397 implements several pseudo opcodes, including several synthetic load
398 instructions.
399
400 @table @code
401
402 @cindex @code{NOP} pseudo op, ARM
403 @item NOP
404 @smallexample
405 nop
406 @end smallexample
407
408 This pseudo op will always evaluate to a legal ARM instruction that does
409 nothing. Currently it will evaluate to MOV r0, r0.
410
411 @cindex @code{LDR reg,=<label>} pseudo op, ARM
412 @item LDR
413 @smallexample
414 ldr <register> , = <expression>
415 @end smallexample
416
417 If expression evaluates to a numeric constant then a MOV or MVN
418 instruction will be used in place of the LDR instruction, if the
419 constant can be generated by either of these instructions. Otherwise
420 the constant will be placed into the nearest literal pool (if it not
421 already there) and a PC relative LDR instruction will be generated.
422
423 @cindex @code{ADR reg,<label>} pseudo op, ARM
424 @item ADR
425 @smallexample
426 adr <register> <label>
427 @end smallexample
428
429 This instruction will load the address of @var{label} into the indicated
430 register. The instruction will evaluate to a PC relative ADD or SUB
431 instruction depending upon where the label is located. If the label is
432 out of range, or if it is not defined in the same file (and section) as
433 the ADR instruction, then an error will be generated. This instruction
434 will not make use of the literal pool.
435
436 @cindex @code{ADRL reg,<label>} pseudo op, ARM
437 @item ADRL
438 @smallexample
439 adrl <register> <label>
440 @end smallexample
441
442 This instruction will load the address of @var{label} into the indicated
443 register. The instruction will evaluate to one or two PC relative ADD
444 or SUB instructions depending upon where the label is located. If a
445 second instruction is not needed a NOP instruction will be generated in
446 its place, so that this instruction is always 8 bytes long.
447
448 If the label is out of range, or if it is not defined in the same file
449 (and section) as the ADRL instruction, then an error will be generated.
450 This instruction will not make use of the literal pool.
451
452 @end table
453
454 For information on the ARM or Thumb instruction sets, see @cite{ARM
455 Software Development Toolkit Reference Manual}, Advanced RISC Machines
456 Ltd.
457
458 @node ARM Mapping Symbols
459 @section Mapping Symbols
460
461 The ARM ELF specification requires that special symbols be inserted
462 into object files to mark certain features:
463
464 @table @code
465
466 @cindex @code{$a}
467 @item $a
468 At the start of a region of code containing ARM instructions.
469
470 @cindex @code{$t}
471 @item $t
472 At the start of a region of code containing THUMB instructions.
473
474 @cindex @code{$d}
475 @item $d
476 At the start of a region of data.
477
478 @end table
479
480 The assembler will automatically insert these symbols for you - there
481 is no need to code them yourself. Support for tagging symbols ($b,
482 $f, $p and $m) which is also mentioned in the current ARM ELF
483 specification is not implemented. This is because they have been
484 dropped from the new EABI and so tools cannot rely upon their
485 presence.
486
This page took 0.040906 seconds and 5 git commands to generate.