*** empty log message ***
[deliverable/binutils-gdb.git] / gas / doc / c-i860.texi
CommitLineData
14218d5f 1@c Copyright 2000, 2003 Free Software Foundation, Inc.
e3308d0d
JE
2@c This is part of the GAS manual.
3@c For copying conditions, see the file as.texinfo.
4@ifset GENERIC
5@page
6@node i860-Dependent
7@chapter Intel i860 Dependent Features
8@end ifset
9@ifclear GENERIC
10@node Machine Dependencies
11@chapter Intel i860 Dependent Features
12@end ifclear
13
14@ignore
15@c FIXME: This is basically a stub for i860. There is tons more information
87505968 16that I will add later (jle@cygnus.com).
e3308d0d
JE
17@end ignore
18
19@cindex i860 support
20@menu
a9c99419 21* Notes-i860:: i860 Notes
e3308d0d
JE
22* Options-i860:: i860 Command-line Options
23* Directives-i860:: i860 Machine Directives
24* Opcodes for i860:: i860 Opcodes
25@end menu
26
a9c99419
JE
27@node Notes-i860
28@section i860 Notes
29This is a fairly complete i860 assembler which is compatible with the
30UNIX System V/860 Release 4 assembler. However, it does not currently
31support SVR4 PIC (i.e., @code{@@GOT, @@GOTOFF, @@PLT}).
e3308d0d 32
a9c99419
JE
33Like the SVR4/860 assembler, the output object format is ELF32. Currently,
34this is the only supported object format. If there is sufficient interest,
35other formats such as COFF may be implemented.
87505968
JE
36
37Both the Intel and AT&T/SVR4 syntaxes are supported, with the latter
38being the default. One difference is that AT&T syntax requires the '%'
39prefix on register names while Intel syntax does not. Another difference
40is in the specification of relocatable expressions. The Intel syntax
41is @code{ha%expression} whereas the SVR4 syntax is @code{[expression]@@ha}
42(and similarly for the "l" and "h" selectors).
a9c99419 43@node Options-i860
e3308d0d
JE
44@section i860 Command-line Options
45@subsection SVR4 compatibility options
46@table @code
47@item -V
48Print assembler version.
49@item -Qy
50Ignored.
51@item -Qn
52Ignored.
53@end table
54@subsection Other options
55@table @code
56@item -EL
57Select little endian output (this is the default).
58@item -EB
59Select big endian output. Note that the i860 always reads instructions
60as little endian data, so this option only effects data and not
61instructions.
a9c99419
JE
62@item -mwarn-expand
63Emit a warning message if any pseudo-instruction expansions occurred.
64For example, a @code{or} instruction with an immediate larger than 16-bits
65will be expanded into two instructions. This is a very undesirable feature to
66rely on, so this flag can help detect any code where it happens. One
67use of it, for instance, has been to find and eliminate any place
68where @code{gcc} may emit these pseudo-instructions.
14218d5f
JE
69@item -mxp
70Enable support for the i860XP instructions and control registers. By default,
71this option is disabled so that only the base instruction set (i.e., i860XR)
72is supported.
87505968
JE
73@item -mintel-syntax
74The i860 assembler defaults to AT&T/SVR4 syntax. This option enables the
75Intel syntax.
e3308d0d
JE
76@end table
77
78@node Directives-i860
79@section i860 Machine Directives
80
81@cindex machine directives, i860
82@cindex i860 machine directives
83
84@table @code
85@cindex @code{dual} directive, i860
86@item .dual
87Enter dual instruction mode. While this directive is supported, the
88preferred way to use dual instruction mode is to explicitly code
89the dual bit with the @code{d.} prefix.
90@end table
91
92@table @code
93@cindex @code{enddual} directive, i860
94@item .enddual
95Exit dual instruction mode. While this directive is supported, the
96preferred way to use dual instruction mode is to explicitly code
97the dual bit with the @code{d.} prefix.
98@end table
99
100@table @code
101@cindex @code{atmp} directive, i860
102@item .atmp
103Change the temporary register used when expanding pseudo operations. The
104default register is @code{r31}.
105@end table
106
5eb0723a
JE
107The @code{.dual}, @code{.enddual}, and @code{.atmp} directives are available only in the Intel syntax mode.
108
820aff55
JE
109Both syntaxes allow for the standard @code{.align} directive. However,
110the Intel syntax additionally allows keywords for the alignment
111parameter: "@code{.align type}", where `type' is one of @code{.short}, @code{.long},
112@code{.quad}, @code{.single}, @code{.double} representing alignments of 2, 4,
11316, 4, and 8, respectively.
114
e3308d0d
JE
115@node Opcodes for i860
116@section i860 Opcodes
117
118@cindex opcodes, i860
119@cindex i860 opcodes
14218d5f 120All of the Intel i860XR and i860XP machine instructions are supported. Please see
a9c99419
JE
121either @emph{i860 Microprocessor Programmer's Reference Manual} or @emph{i860 Microprocessor Architecture} for more information.
122@subsection Other instruction support (pseudo-instructions)
123For compatibility with some other i860 assemblers, a number of
124pseudo-instructions are supported. While these are supported, they are
125a very undesirable feature that should be avoided -- in particular, when
126they result in an expansion to multiple actual i860 instructions. Below
127are the pseudo-instructions that result in expansions.
128@itemize @bullet
9fc2dda2 129@item Load large immediate into general register:
a9c99419
JE
130
131The pseudo-instruction @code{mov imm,%rn} (where the immediate does
132not fit within a signed 16-bit field) will be expanded into:
133@smallexample
134orh large_imm@@h,%r0,%rn
135or large_imm@@l,%rn,%rn
136@end smallexample
9fc2dda2 137@item Load/store with relocatable address expression:
a9c99419 138
0dee3be0 139For example, the pseudo-instruction @code{ld.b addr_exp(%rx),%rn}
a9c99419
JE
140will be expanded into:
141@smallexample
0dee3be0 142orh addr_exp@@ha,%rx,%r31
a9c99419
JE
143ld.l addr_exp@@l(%r31),%rn
144@end smallexample
145
146The analogous expansions apply to @code{ld.x, st.x, fld.x, pfld.x, fst.x}, and @code{pst.x} as well.
9fc2dda2
JE
147@item Signed large immediate with add/subtract:
148
a9c99419
JE
149If any of the arithmetic operations @code{adds, addu, subs, subu} are used
150with an immediate larger than 16-bits (signed), then they will be expanded.
151For instance, the pseudo-instruction @code{adds large_imm,%rx,%rn} expands to:
152@smallexample
153orh large_imm@@h,%r0,%r31
154or large_imm@@l,%r31,%r31
155adds %r31,%rx,%rn
156@end smallexample
9fc2dda2
JE
157@item Unsigned large immediate with logical operations:
158
a9c99419
JE
159Logical operations (@code{or, andnot, or, xor}) also result in expansions.
160The pseudo-instruction @code{or large_imm,%rx,%rn} results in:
161@smallexample
162orh large_imm@@h,%rx,%r31
163or large_imm@@l,%r31,%rn
164@end smallexample
e3308d0d 165
a9c99419
JE
166Similarly for the others, except for @code{and} which expands to:
167@smallexample
168andnot (-1 - large_imm)@@h,%rx,%r31
169andnot (-1 - large_imm)@@l,%r31,%rn
170@end smallexample
171@end itemize
e3308d0d 172
This page took 0.311288 seconds and 4 git commands to generate.