Subversion Repositories open8_urisc

@c Copyright 2005, 2006, 2009, 2010, 2011

@c Free Software Foundation, Inc.

@c This is part of the GAS manual.

@c For copying conditions, see the file as.texinfo.

@c man end

@ifset GENERIC

@page

@node Blackfin-Dependent

@chapter Blackfin Dependent Features

@end ifset

@ifclear GENERIC

@node Machine Dependencies

@chapter Blackfin Dependent Features

@end ifclear

@cindex Blackfin support

@menu

* Blackfin Options::            Blackfin Options

* Blackfin Syntax::             Blackfin Syntax

* Blackfin Directives::         Blackfin Directives

@end menu

@node Blackfin Options

@section Options

@cindex Blackfin options (none)

@cindex options for Blackfin (none)

@c man begin OPTIONS

@table @gcctabopt

@cindex @code{-mcpu=} command line option, Blackfin

@item -mcpu=@var{processor}@r{[}-@var{sirevision}@r{]}

This option specifies the target processor.  The optional @var{sirevision}

is not used in assembler.  It's here such that GCC can easily pass down its

@code{-mcpu=} option.  The assembler will issue an

error message if an attempt is made to assemble an instruction which

will not execute on the target processor.  The following processor names are

recognized:

@code{bf504},

@code{bf506},

@code{bf512},

@code{bf514},

@code{bf516},

@code{bf518},

@code{bf522},

@code{bf523},

@code{bf524},

@code{bf525},

@code{bf526},

@code{bf527},

@code{bf531},

@code{bf532},

@code{bf533},

@code{bf534},

@code{bf535} (not implemented yet),

@code{bf536},

@code{bf537},

@code{bf538},

@code{bf539},

@code{bf542},

@code{bf542m},

@code{bf544},

@code{bf544m},

@code{bf547},

@code{bf547m},

@code{bf548},

@code{bf548m},

@code{bf549},

@code{bf549m},

@code{bf561},

and

@code{bf592}.

@cindex @code{-mfdpic} command line option, Blackfin

@item -mfdpic

Assemble for the FDPIC ABI.

@cindex @code{-mno-fdpic} command line option, Blackfin

@cindex @code{-mnopic} command line option, Blackfin

@item -mno-fdpic

@itemx -mnopic

Disable -mfdpic.

@end table

@c man end

@node Blackfin Syntax

@section Syntax

@cindex Blackfin syntax

@cindex syntax, Blackfin

@table @code

@item Special Characters

Assembler input is free format and may appear anywhere on the line.

One instruction may extend across multiple lines or more than one

instruction may appear on the same line.  White space (space, tab,

comments or newline) may appear anywhere between tokens.  A token must

not have embedded spaces.  Tokens include numbers, register names,

keywords, user identifiers, and also some multicharacter special

symbols like "+=", "/*" or "||".

Comments are introduced by the @samp{#} character and extend to the

end of the current line.  If the @samp{#} appears as the first

character of a line, the whole line is treated as a comment, but in

this case the line can also be a logical line number directive

(@pxref{Comments}) or a preprocessor control command

(@pxref{Preprocessing}).

@item Instruction Delimiting

A semicolon must terminate every instruction.  Sometimes a complete

instruction will consist of more than one operation.  There are two

cases where this occurs.  The first is when two general operations

are combined.  Normally a comma separates the different parts, as in

@smallexample

a0= r3.h * r2.l, a1 = r3.l * r2.h ;

@end smallexample

The second case occurs when a general instruction is combined with one

or two memory references for joint issue.  The latter portions are

set off by a "||" token.

@smallexample

a0 = r3.h * r2.l || r1 = [p3++] || r4 = [i2++];

@end smallexample

Multiple instructions can occur on the same line.  Each must be

terminated by a semicolon character.

@item Register Names

The assembler treats register names and instruction keywords in a case

insensitive manner.  User identifiers are case sensitive.  Thus, R3.l,

R3.L, r3.l and r3.L are all equivalent input to the assembler.

Register names are reserved and may not be used as program identifiers.

Some operations (such as "Move Register") require a register pair.

Register pairs are always data registers and are denoted using a colon,

eg., R3:2.  The larger number must be written firsts.  Note that the

hardware only supports odd-even pairs, eg., R7:6, R5:4, R3:2, and R1:0.

Some instructions (such as --SP (Push Multiple)) require a group of

adjacent registers.  Adjacent registers are denoted in the syntax by

the range enclosed in parentheses and separated by a colon, eg., (R7:3).

Again, the larger number appears first.

Portions of a particular register may be individually specified.  This

is written with a dot (".") following the register name and then a

letter denoting the desired portion.  For 32-bit registers, ".H"

denotes the most significant ("High") portion.  ".L" denotes the

least-significant portion.  The subdivisions of the 40-bit registers

are described later.

@item Accumulators

The set of 40-bit registers A1 and A0 that normally contain data that

is being manipulated.  Each accumulator can be accessed in four ways.

@table @code

@item one 40-bit register

The register will be referred to as A1 or A0.

@item one 32-bit register

The registers are designated as A1.W or A0.W.

@item two 16-bit registers

The registers are designated as A1.H, A1.L, A0.H or A0.L.

@item one 8-bit register

The registers are designated as A1.X or A0.X for the bits that

extend beyond bit 31.

@end table

@item Data Registers

The set of 32-bit registers (R0, R1, R2, R3, R4, R5, R6 and R7) that

normally contain data for manipulation.  These are abbreviated as

D-register or Dreg.  Data registers can be accessed as 32-bit registers

or as two independent 16-bit registers.  The least significant 16 bits

of each register is called the "low" half and is designated with ".L"

following the register name.  The most significant 16 bits are called

the "high" half and is designated with ".H" following the name.

@smallexample

   R7.L, r2.h, r4.L, R0.H

@end smallexample

@item Pointer Registers

The set of 32-bit registers (P0, P1, P2, P3, P4, P5, SP and FP) that

normally contain byte addresses of data structures.  These are

abbreviated as P-register or Preg.

@smallexample

p2, p5, fp, sp

@end smallexample

@item Stack Pointer SP

The stack pointer contains the 32-bit address of the last occupied

byte location in the stack.  The stack grows by decrementing the

stack pointer.

@item Frame Pointer FP

The frame pointer contains the 32-bit address of the previous frame

pointer in the stack.  It is located at the top of a frame.

@item Loop Top

LT0 and LT1.  These registers contain the 32-bit address of the top of

a zero overhead loop.

@item Loop Count

LC0 and LC1.  These registers contain the 32-bit counter of the zero

overhead loop executions.

@item Loop Bottom

LB0 and LB1.  These registers contain the 32-bit address of the bottom

of a zero overhead loop.

@item Index Registers

The set of 32-bit registers (I0, I1, I2, I3) that normally contain byte

addresses of data structures.  Abbreviated I-register or Ireg.

@item Modify Registers

The set of 32-bit registers (M0, M1, M2, M3) that normally contain

offset values that are added and subtracted to one of the index

registers.  Abbreviated as Mreg.

@item Length Registers

The set of 32-bit registers (L0, L1, L2, L3) that normally contain the

length in bytes of the circular buffer.  Abbreviated as Lreg.  Clear

the Lreg to disable circular addressing for the corresponding Ireg.

@item Base Registers

The set of 32-bit registers (B0, B1, B2, B3) that normally contain the

base address in bytes of the circular buffer.  Abbreviated as Breg.

@item Floating Point

The Blackfin family has no hardware floating point but the .float

directive generates ieee floating point numbers for use with software

floating point libraries.

@item Blackfin Opcodes

For detailed information on the Blackfin machine instruction set, see

the Blackfin(r) Processor Instruction Set Reference.

@end table

@node Blackfin Directives

@section Directives

@cindex Blackfin directives

@cindex directives, Blackfin

The following directives are provided for compatibility with the VDSP assembler.

@table @code

@item .byte2

Initializes a two byte data object.

This maps to the @code{.short} directive.

@item .byte4

Initializes a four byte data object.

This maps to the @code{.int} directive.

@item .db

Initializes a single byte data object.

This directive is a synonym for @code{.byte}.

@item .dw

Initializes a two byte data object.

This directive is a synonym for @code{.byte2}.

@item .dd

Initializes a four byte data object.

This directive is a synonym for @code{.byte4}.

@item .var

Define and initialize a 32 bit data object.

@end table