📄 d30v-size.html

📁 gcc手册

💻 HTML

字号:

<html lang="en">

<head>

<title>Using as</title>

<meta http-equiv="Content-Type" content="text/html">

<meta name="description" content="Using as">

<meta name="generator" content="makeinfo 4.3">

<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">

</head>

<body>

<div class="node">

<p>

Node:<a name="D30V-Size">D30V-Size</a>,

Next:<a rel="next" accesskey="n" href="D30V-Subs.html#D30V-Subs">D30V-Subs</a>,

Up:<a rel="up" accesskey="u" href="D30V-Syntax.html#D30V-Syntax">D30V-Syntax</a>

<hr><br>

</div>



<h5 class="subsection">Size Modifiers</h5>



   <p>The D30V version of <code>as</code> uses the instruction names in the D30V

Architecture Manual.  However, the names in the manual are sometimes ambiguous. 

There are instruction names that can assemble to a short or long form opcode. 

How does the assembler pick the correct form?  <code>as</code> will always pick the

smallest form if it can.  When dealing with a symbol that is not defined yet when a

line is being assembled, it will always use the long form.  If you need to force the

assembler to use either the short or long form of the instruction, you can append

either <code>.s</code> (short) or <code>.l</code> (long) to it.  For example, if you are writing

an assembly program and you want to do a branch to a symbol that is defined later

in your program, you can write <code>bra.s foo</code>. 

Objdump and GDB will always append <code>.s</code> or <code>.l</code> to instructions which

have both short and long forms.



   </body></html>

⌨️ 快捷键说明

复制代码 Ctrl + C

搜索代码 Ctrl + F

全屏模式 F11

切换主题 Ctrl + Shift + D

显示快捷键 ?

增大字号 Ctrl + =

减小字号 Ctrl + -