?? x-ppc2.html
字號:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> PowerPC </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="GuideIX.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="x-ppc.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="x-ppc1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="x-ppc3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="84381">F.2 Building Applications</a></i></h3></font><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="84977"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>The compiler for PowerPC conforms to the Embedded Application Binary Interface (EABI) protocol. Therefore type checking is more rigorous than for other architectures.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dl class="margin"><dd><p class="Body"><a name="84391"> </a>The Tornado 2.0 project facility is correctly preconfigured for building WRS BSPs. However, if you choose not to use the project facility or if you need to customize your build, you may need the information in the following sections. This includes a configuration constant, an environment variable, and compiler options that together specify the information the GNU toolkit requires to compile correctly for PowerPC targets.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84394">Defining the CPU Type</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84395"> </a>Setting the preprocessor variable <b class="symbol_UC">CPU</b> ensures that VxWorks and your applications are compiled with the appropriate architecture-specific features enabled. This variable should be set to one of the following values, depending on the processor you are using:</p></dl><dl class="margin"><ul class="DashSingle" type="circle"><li><a name="84396"> </a><b class="symbol_UC">PPC403</b> </li></ul><ul class="DashSingle" type="circle"><li><a name="84397"> </a><b class="symbol_UC">PPC603</b> </li></ul><ul class="DashSingle" type="circle"><li><a name="84398"> </a><b class="symbol_UC">PPC604</b> </li></ul><ul class="DashSingle" type="circle"><li><a name="84399"> </a><b class="symbol_UC">PPC860</b> </li></ul></dl><dl class="margin"><dd><p class="Body"><a name="84400"> </a>For example, to specify <b class="symbol_UC">CPU</b> for a PowerPC 603 on the compiler command line, use the following command-line option when you invoke the compiler:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84401">-DCPU=PPC603</a></b></pre></dl><dd><p class="Body"><a name="84402"> </a>To provide the same information in a header or source file, include the following line in the file:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84403">#define CPU PPC603</a></b></pre></dl><dd><p class="Body"><a name="84404"> </a>All VxWorks makefiles pass along the definition of this variable to the compiler. You can define <b class="symbol_UC">CPU</b> on the <b class="command">make</b> command line as follows:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84406"></b><tt class="output">%</tt><b> make CPU=PPC603 </a></b></pre></dl><dd><p class="Body"><a name="84407"> </a>You can also set the definition directly in a makefile, with the following line:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84408">CPU=PPC603</a></b></pre></dl></dl></dl><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/caution.gif"></td><td><hr><div class="CalloutCell"><a name="84993"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">CAUTION: </font></b></a>If you are using a PowerPC 821 processor, define <b class="symbol_UC">CPU</b> to be <b class="symbol_UC">PPC860</b>.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84419">Configuring the GNU ToolKit Environment</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84420"> </a>Tornado includes the GNU compiler and associated tools. Tornado is configured to use these tools by default. No change is required to the execution path, because the compilation chain is installed in the same <b class="file">bin</b> directory as the other Tornado executables. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84421">Compiling C and C++ Modules</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84423"> </a>The following is an example of a compiler command line for PowerPC 603 cross-development. The file to be compiled in this example has a base name of <b class="file">applic</b>.</p><dl class="margin"><dd><pre class="Code2"><b><a name="84424"></b><tt class="output">% </tt><b>ccppc -O2 -mcpu=603 -I$WIND_BASE/target/h -fno-builtin \ -fno-for-scope -nostdinc -DCPU=PPC603 -D_GNU_TOOL -c applic.<i class="textVariable">language_id</i></a></b></pre></dl><dd><p class="Body"><a name="84425"> </a>The options shown in the example have the following meanings:</p></dl><dl class="margin"><dd><div class="Item"><a name="84427"> </a><b class="symbol_lc">-O2</b> </div><dl class="margin"><dd><div class="Indent"><a name="84428"> </a>Optional; performs level 2 optimization.</div><br></dl><dd><div class="Item"><a name="84430"> </a><b class="symbol_lc">-mcpu=603</b> </div><dl class="margin"><dd><div class="Indent"><a name="84431"> </a>Optional for 603 and 604; required for other processors (specify the appropriate processor values: <b class="command">601</b>, <b class="command">403</b>,<b class="command"> 860</b>, or<b class="command"> 821</b>); instructs the compiler to produce code for the specified PowerPC architecture. The default is 604, which applies to 603 as well.</div><br></dl><dd><div class="Item"><a name="84433"> </a><b class="symbol_lc">-I</b><b class="symbol_UC">$WIND_BASE</b><b class="symbol_lc">/target/h</b> </div><dl class="margin"><dd><div class="Indent"><a name="84434"> </a>Required; gives access to the VxWorks include files. (Additional <br><b class="command">-I</b> flags may be included to specify other header files.)</div><br></dl><dd><div class="Item"><a name="84436"> </a><b class="symbol_lc">-fno-builtin</b> </div><dl class="margin"><dd><div class="Indent"><a name="84437"> </a>Required; uses library calls even for common library subroutines.</div><br></dl><dd><div class="Item"><a name="84439"> </a><b class="symbol_lc">-fno-for-scope</b> </div><dl class="margin"><dd><div class="Indent"><a name="84440"> </a>Required; allows the scope of variables declared within a for loop to be outside of the for loop.</div><br></dl><dd><div class="Item"><a name="84442"> </a><b class="symbol_lc">-nostdinc</b> </div><dl class="margin"><dd><div class="Indent"><a name="84443"> </a>Required; searches only the directory or directories specified with the <b class="command">-I </b>flag (see above) and the current directory for header files. It does not search host-system include files.</div><br></dl><dd><div class="Item"><a name="84445"> </a><b class="symbol_UC">-DCPU=PPC603</b> </div><dl class="margin"><dd><div class="Indent"><a name="84446"> </a>Required; defines the CPU type. If you are using another PowerPC processor, specify the appropriate value (see <a href="x-ppc2.html#84394"><i class="title">Defining the CPU Type</i></a>).</div><br></dl><dd><div class="Item"><a name="84451"> </a>-<b class="symbol_UC">D_GNU_TOOL</b> </div><dl class="margin"><dd><div class="Indent"><a name="84452"> </a>Required; defines the compilation toolkit used to compile VxWorks or applications.</div><br></dl><dd><div class="Item"><a name="84454"> </a><b class="symbol_lc">-c</b> </div><dl class="margin"><dd><div class="Indent"><a name="84455"> </a>Required; specifies that the module is to be compiled only, and not linked for execution under the host. </div><br></dl><dd><div class="Item"><a name="84457"> </a><b class="file">applic</b><i class="textVariable">.language_id</i> </div><dl class="margin"><dd><div class="Indent"><a name="84458"> </a>Required; specifies the file(s) to compile. For C compilation, specify a suffix of <b class="command">.c</b>. For C++ compilations, specifies a suffix of <b class="file">.cpp</b>. The output is an unlinked object module in <b class="symbol_UC">ELF</b> format with the suffix <b class="file">.o</b>. For the example above, the output would be <b class="file">applic.o</b>. </div><br></dl></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84461">Compiling Modules for GDB</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84463"> </a>To compile C modules for debugging in GDB, we recommend using the <b class="command">-gdwarf </b>flag to generate DWARF debug information instead of the<b class="command"> -g</b> flag, which generates STABS information. For example:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84465"></b><tt class="output">%</tt><b> ccppc -mcpu=603 -I$WIND_BASE/target/h -fno-builtin -nostdinc \ -DCPU=PPC603 -c -gdwarf test.c</a></b></pre></dl><dd><p class="Body"><a name="84466"> </a>where <b class="symbol_UC">$WIND_BASE </b>is the location of your Tornado tree and <b class="symbol_UC">-DCPU</b> specifies the CPU type.</p><dd><p class="Body"><a name="84467"> </a>The compiler does not support DWARF debug information for C++. If you are using C++, you must use the <b>-g</b> flag:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84468"></b><tt class="output">%</tt><b> ccppc -mcpu=603 -I$WIND_BASE/target/h -fno-builtin -nostdinc \ -DCPU=PPC603 -c -g test.cpp</a></b></pre></dl></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84469">Unsupported Features</a></i></h4></font><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="84470">Prefixed Underscore</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="84472"> </a>In the PowerPC architecture, the compiler does not prefix underscores to symbols. In other words, <b class="symbol_lc">symbol</b> is not equivalent to <b class="symbol_lc">_symbol</b> as it is in other architecture implementations.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="84473">Small Data Area</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="84475"> </a>The compiler supports the small data area. However, for this release of Tornado for PowerPC, VxWorks does not support the small data area. Therefore the <b class="command">-msdata</b> compiler flag must not be used.</p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="GuideIX.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="x-ppc.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="x-ppc1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="x-ppc3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -