mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-05-13 17:38:39 +00:00
Reflow and clean up some of the HTML in the initial section, split linkage
types into its own section. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@18697 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner
parent
fa73021cf1
commit
e5d947bc84
@ -20,6 +20,7 @@
|
|||||||
<li><a href="#highlevel">High Level Structure</a>
|
<li><a href="#highlevel">High Level Structure</a>
|
||||||
<ol>
|
<ol>
|
||||||
<li><a href="#modulestructure">Module Structure</a></li>
|
<li><a href="#modulestructure">Module Structure</a></li>
|
||||||
|
<li><a href="#linkage">Linkage Types</a></li>
|
||||||
<li><a href="#globalvars">Global Variables</a></li>
|
<li><a href="#globalvars">Global Variables</a></li>
|
||||||
<li><a href="#functionstructure">Function Structure</a></li>
|
<li><a href="#functionstructure">Function Structure</a></li>
|
||||||
</ol>
|
</ol>
|
||||||
@ -220,66 +221,88 @@ the parser.</p>
|
|||||||
purposes:</p>
|
purposes:</p>
|
||||||
|
|
||||||
<ol>
|
<ol>
|
||||||
<li>Numeric constants are represented as you would expect: 12, -3
|
<li>Numeric constants are represented as you would expect: 12, -3 123.421,
|
||||||
123.421, etc. Floating point constants have an optional hexadecimal
|
etc. Floating point constants have an optional hexadecimal notation.</li>
|
||||||
notation.</li>
|
|
||||||
<li>Named values are represented as a string of characters with a '%'
|
<li>Named values are represented as a string of characters with a '%' prefix.
|
||||||
prefix. For example, %foo, %DivisionByZero,
|
For example, %foo, %DivisionByZero, %a.really.long.identifier. The actual
|
||||||
%a.really.long.identifier. The actual regular expression used is '<tt>%[a-zA-Z$._][a-zA-Z$._0-9]*</tt>'.
|
regular expression used is '<tt>%[a-zA-Z$._][a-zA-Z$._0-9]*</tt>'.
|
||||||
Identifiers which require other characters in their names can be
|
Identifiers which require other characters in their names can be surrounded
|
||||||
surrounded with quotes. In this way, anything except a <tt>"</tt>
|
with quotes. In this way, anything except a <tt>"</tt> character can be used
|
||||||
character can be used in a name.</li>
|
in a name.</li>
|
||||||
<li>Unnamed values are represented as an unsigned numeric value with
|
|
||||||
a '%' prefix. For example, %12, %2, %44.</li>
|
<li>Unnamed values are represented as an unsigned numeric value with a '%'
|
||||||
|
prefix. For example, %12, %2, %44.</li>
|
||||||
|
|
||||||
</ol>
|
</ol>
|
||||||
<p>LLVM requires that values start with a '%' sign for two reasons:
|
|
||||||
Compilers don't need to worry about name clashes with reserved words,
|
<p>LLVM requires that values start with a '%' sign for two reasons: Compilers
|
||||||
and the set of reserved words may be expanded in the future without
|
don't need to worry about name clashes with reserved words, and the set of
|
||||||
penalty. Additionally, unnamed identifiers allow a compiler to quickly
|
reserved words may be expanded in the future without penalty. Additionally,
|
||||||
come up with a temporary variable without having to avoid symbol table
|
unnamed identifiers allow a compiler to quickly come up with a temporary
|
||||||
conflicts.</p>
|
variable without having to avoid symbol table conflicts.</p>
|
||||||
|
|
||||||
<p>Reserved words in LLVM are very similar to reserved words in other
|
<p>Reserved words in LLVM are very similar to reserved words in other
|
||||||
languages. There are keywords for different opcodes ('<tt><a
|
languages. There are keywords for different opcodes ('<tt><a
|
||||||
href="#i_add">add</a></tt>', '<tt><a href="#i_cast">cast</a></tt>', '<tt><a
|
href="#i_add">add</a></tt>', '<tt><a href="#i_cast">cast</a></tt>', '<tt><a
|
||||||
href="#i_ret">ret</a></tt>', etc...), for primitive type names ('<tt><a
|
href="#i_ret">ret</a></tt>', etc...), for primitive type names ('<tt><a
|
||||||
href="#t_void">void</a></tt>', '<tt><a href="#t_uint">uint</a></tt>',
|
href="#t_void">void</a></tt>', '<tt><a href="#t_uint">uint</a></tt>', etc...),
|
||||||
etc...), and others. These reserved words cannot conflict with
|
and others. These reserved words cannot conflict with variable names, because
|
||||||
variable names, because none of them start with a '%' character.</p>
|
none of them start with a '%' character.</p>
|
||||||
<p>Here is an example of LLVM code to multiply the integer variable '<tt>%X</tt>'
|
|
||||||
by 8:</p>
|
<p>Here is an example of LLVM code to multiply the integer variable
|
||||||
|
'<tt>%X</tt>' by 8:</p>
|
||||||
|
|
||||||
<p>The easy way:</p>
|
<p>The easy way:</p>
|
||||||
<pre> %result = <a href="#i_mul">mul</a> uint %X, 8<br></pre>
|
|
||||||
|
<pre>
|
||||||
|
%result = <a href="#i_mul">mul</a> uint %X, 8
|
||||||
|
</pre>
|
||||||
|
|
||||||
<p>After strength reduction:</p>
|
<p>After strength reduction:</p>
|
||||||
<pre> %result = <a href="#i_shl">shl</a> uint %X, ubyte 3<br></pre>
|
|
||||||
|
<pre>
|
||||||
|
%result = <a href="#i_shl">shl</a> uint %X, ubyte 3
|
||||||
|
</pre>
|
||||||
|
|
||||||
<p>And the hard way:</p>
|
<p>And the hard way:</p>
|
||||||
<pre> <a href="#i_add">add</a> uint %X, %X <i>; yields {uint}:%0</i>
|
|
||||||
<a
|
<pre>
|
||||||
href="#i_add">add</a> uint %0, %0 <i>; yields {uint}:%1</i>
|
<a href="#i_add">add</a> uint %X, %X <i>; yields {uint}:%0</i>
|
||||||
%result = <a
|
<a href="#i_add">add</a> uint %0, %0 <i>; yields {uint}:%1</i>
|
||||||
href="#i_add">add</a> uint %1, %1<br></pre>
|
%result = <a href="#i_add">add</a> uint %1, %1
|
||||||
|
</pre>
|
||||||
|
|
||||||
<p>This last way of multiplying <tt>%X</tt> by 8 illustrates several
|
<p>This last way of multiplying <tt>%X</tt> by 8 illustrates several
|
||||||
important lexical features of LLVM:</p>
|
important lexical features of LLVM:</p>
|
||||||
|
|
||||||
<ol>
|
<ol>
|
||||||
<li>Comments are delimited with a '<tt>;</tt>' and go until the end
|
|
||||||
of line.</li>
|
<li>Comments are delimited with a '<tt>;</tt>' and go until the end of
|
||||||
<li>Unnamed temporaries are created when the result of a computation
|
line.</li>
|
||||||
is not assigned to a named value.</li>
|
|
||||||
|
<li>Unnamed temporaries are created when the result of a computation is not
|
||||||
|
assigned to a named value.</li>
|
||||||
|
|
||||||
<li>Unnamed temporaries are numbered sequentially</li>
|
<li>Unnamed temporaries are numbered sequentially</li>
|
||||||
|
|
||||||
</ol>
|
</ol>
|
||||||
<p>...and it also show a convention that we follow in this document.
|
|
||||||
When demonstrating instructions, we will follow an instruction with a
|
<p>...and it also show a convention that we follow in this document. When
|
||||||
comment that defines the type and name of value produced. Comments are
|
demonstrating instructions, we will follow an instruction with a comment that
|
||||||
shown in italic text.</p>
|
defines the type and name of value produced. Comments are shown in italic
|
||||||
<p>The one non-intuitive notation for constants is the optional
|
text.</p>
|
||||||
hexidecimal form of floating point constants. For example, the form '<tt>double
|
|
||||||
|
<p>The one non-intuitive notation for constants is the optional hexidecimal form
|
||||||
|
of floating point constants. For example, the form '<tt>double
|
||||||
0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
|
0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
|
||||||
4.5e+15</tt>' which is also supported by the parser. The only time
|
4.5e+15</tt>' which is also supported by the parser. The only time hexadecimal
|
||||||
hexadecimal floating point constants are useful (and the only time that
|
floating point constants are useful (and the only time that they are generated
|
||||||
they are generated by the disassembler) is when an FP constant has to
|
by the disassembler) is when an FP constant has to be emitted that is not
|
||||||
be emitted that is not representable as a decimal floating point number
|
representable as a decimal floating point number exactly. For example, NaN's,
|
||||||
exactly. For example, NaN's, infinities, and other special cases are
|
infinities, and other special cases are represented in their IEEE hexadecimal
|
||||||
represented in their IEEE hexadecimal format so that assembly and
|
format so that assembly and disassembly do not cause any bits to change in the
|
||||||
disassembly do not cause any bits to change in the constants.</p>
|
constants.</p>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<!-- *********************************************************************** -->
|
<!-- *********************************************************************** -->
|
||||||
@ -323,59 +346,70 @@ named "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>"
|
|||||||
function, and a <a href="#functionstructure">function definition</a>
|
function, and a <a href="#functionstructure">function definition</a>
|
||||||
for "<tt>main</tt>".</p>
|
for "<tt>main</tt>".</p>
|
||||||
|
|
||||||
<a name="linkage"> In general, a module is made up of a list of global
|
<p>In general, a module is made up of a list of global values,
|
||||||
values, where both functions and global variables are global values.
|
where both functions and global variables are global values. Global values are
|
||||||
Global values are represented by a pointer to a memory location (in
|
represented by a pointer to a memory location (in this case, a pointer to an
|
||||||
this case, a pointer to an array of char, and a pointer to a function),
|
array of char, and a pointer to a function), and have one of the following <a
|
||||||
and have one of the following linkage types:</a>
|
href="#linkage">linkage types</a>.</p>
|
||||||
|
|
||||||
<p> </p>
|
</div>
|
||||||
|
|
||||||
|
<!-- ======================================================================= -->
|
||||||
|
<div class="doc_subsection">
|
||||||
|
<a name="linkage">Linkage Types</a>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
<div class="doc_text">
|
||||||
|
|
||||||
|
<p>
|
||||||
|
All Global Variables and Functions have one of the following types of linkage:
|
||||||
|
</p>
|
||||||
|
|
||||||
<dl>
|
<dl>
|
||||||
|
|
||||||
<dt><tt><b><a name="linkage_internal">internal</a></b></tt> </dt>
|
<dt><tt><b><a name="linkage_internal">internal</a></b></tt> </dt>
|
||||||
<dd>Global values with internal linkage are only directly accessible
|
|
||||||
by objects in the current module. In particular, linking code into a
|
<dd>Global values with internal linkage are only directly accessible by
|
||||||
module with an internal global value may cause the internal to be
|
objects in the current module. In particular, linking code into a module with
|
||||||
renamed as necessary to avoid collisions. Because the symbol is
|
an internal global value may cause the internal to be renamed as necessary to
|
||||||
internal to the module, all references can be updated. This
|
avoid collisions. Because the symbol is internal to the module, all
|
||||||
corresponds to the notion of the '<tt>static</tt>' keyword in C, or the
|
references can be updated. This corresponds to the notion of the
|
||||||
idea of "anonymous namespaces" in C++.
|
'<tt>static</tt>' keyword in C, or the idea of "anonymous namespaces" in C++.
|
||||||
<p> </p>
|
|
||||||
</dd>
|
</dd>
|
||||||
|
|
||||||
<dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt>: </dt>
|
<dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt>: </dt>
|
||||||
<dd>"<tt>linkonce</tt>" linkage is similar to <tt>internal</tt>
|
|
||||||
linkage, with the twist that linking together two modules defining the
|
<dd>"<tt>linkonce</tt>" linkage is similar to <tt>internal</tt> linkage, with
|
||||||
same <tt>linkonce</tt> globals will cause one of the globals to be
|
the twist that linking together two modules defining the same
|
||||||
discarded. This is typically used to implement inline functions.
|
<tt>linkonce</tt> globals will cause one of the globals to be discarded. This
|
||||||
Unreferenced <tt>linkonce</tt> globals are allowed to be discarded.
|
is typically used to implement inline functions. Unreferenced
|
||||||
<p> </p>
|
<tt>linkonce</tt> globals are allowed to be discarded.
|
||||||
</dd>
|
</dd>
|
||||||
|
|
||||||
<dt><tt><b><a name="linkage_weak">weak</a></b></tt>: </dt>
|
<dt><tt><b><a name="linkage_weak">weak</a></b></tt>: </dt>
|
||||||
<dd>"<tt>weak</tt>" linkage is exactly the same as <tt>linkonce</tt>
|
|
||||||
linkage, except that unreferenced <tt>weak</tt> globals may not be
|
<dd>"<tt>weak</tt>" linkage is exactly the same as <tt>linkonce</tt> linkage,
|
||||||
discarded. This is used to implement constructs in C such as "<tt>int
|
except that unreferenced <tt>weak</tt> globals may not be discarded. This is
|
||||||
X;</tt>" at global scope.
|
used to implement constructs in C such as "<tt>int X;</tt>" at global scope.
|
||||||
<p> </p>
|
|
||||||
</dd>
|
</dd>
|
||||||
|
|
||||||
<dt><tt><b><a name="linkage_appending">appending</a></b></tt>: </dt>
|
<dt><tt><b><a name="linkage_appending">appending</a></b></tt>: </dt>
|
||||||
<dd>"<tt>appending</tt>" linkage may only be applied to global
|
|
||||||
variables of pointer to array type. When two global variables with
|
<dd>"<tt>appending</tt>" linkage may only be applied to global variables of
|
||||||
appending linkage are linked together, the two global arrays are
|
pointer to array type. When two global variables with appending linkage are
|
||||||
appended together. This is the LLVM, typesafe, equivalent of having
|
linked together, the two global arrays are appended together. This is the
|
||||||
the system linker append together "sections" with identical names when
|
LLVM, typesafe, equivalent of having the system linker append together
|
||||||
.o files are linked.
|
"sections" with identical names when .o files are linked.
|
||||||
<p> </p>
|
|
||||||
</dd>
|
</dd>
|
||||||
|
|
||||||
<dt><tt><b><a name="linkage_external">externally visible</a></b></tt>:</dt>
|
<dt><tt><b><a name="linkage_external">externally visible</a></b></tt>:</dt>
|
||||||
<dd>If none of the above identifiers are used, the global is
|
|
||||||
externally visible, meaning that it participates in linkage and can be
|
<dd>If none of the above identifiers are used, the global is externally
|
||||||
used to resolve external symbol references.
|
visible, meaning that it participates in linkage and can be used to resolve
|
||||||
<p> </p>
|
external symbol references.
|
||||||
</dd>
|
</dd>
|
||||||
</dl>
|
</dl>
|
||||||
|
|
||||||
<p> </p>
|
|
||||||
|
|
||||||
<p><a name="linkage_external">For example, since the "<tt>.LC0</tt>"
|
<p><a name="linkage_external">For example, since the "<tt>.LC0</tt>"
|
||||||
variable is defined to be internal, if another module defined a "<tt>.LC0</tt>"
|
variable is defined to be internal, if another module defined a "<tt>.LC0</tt>"
|
||||||
variable and was linked with this one, one of the two would be renamed,
|
variable and was linked with this one, one of the two would be renamed,
|
||||||
@ -383,6 +417,7 @@ preventing a collision. Since "<tt>main</tt>" and "<tt>puts</tt>" are
|
|||||||
external (i.e., lacking any linkage declarations), they are accessible
|
external (i.e., lacking any linkage declarations), they are accessible
|
||||||
outside of the current module. It is illegal for a function <i>declaration</i>
|
outside of the current module. It is illegal for a function <i>declaration</i>
|
||||||
to have any linkage type other than "externally visible".</a></p>
|
to have any linkage type other than "externally visible".</a></p>
|
||||||
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<!-- ======================================================================= -->
|
<!-- ======================================================================= -->
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user