arduino-0018-windows
This commit is contained in:
		
							parent
							
								
									157fd6f1a1
								
							
						
					
					
						commit
						f39fc49523
					
				
					 5182 changed files with 950586 additions and 0 deletions
				
			
		|  | @ -0,0 +1,76 @@ | |||
| <html lang="en"> | ||||
| <head> | ||||
| <title>BFD - Untitled</title> | ||||
| <meta http-equiv="Content-Type" content="text/html"> | ||||
| <meta name="description" content="Untitled"> | ||||
| <meta name="generator" content="makeinfo 4.7"> | ||||
| <link title="Top" rel="start" href="index.html#Top"> | ||||
| <link rel="prev" href="Machine-Dependent.html#Machine-Dependent" title="Machine Dependent"> | ||||
| <link rel="next" href="Reporting-Bugs.html#Reporting-Bugs" title="Reporting Bugs"> | ||||
| <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> | ||||
| <!-- | ||||
| This file documents the GNU linker LD | ||||
| (GNU Binutils) | ||||
| version 2.19. | ||||
| 
 | ||||
| Copyright (C) 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000, | ||||
| 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc. | ||||
| 
 | ||||
| Permission is granted to copy, distribute and/or modify this document | ||||
| under the terms of the GNU Free Documentation License, Version 1.1 | ||||
| or any later version published by the Free Software Foundation; | ||||
| with no Invariant Sections, with no Front-Cover Texts, and with no | ||||
| Back-Cover Texts.  A copy of the license is included in the | ||||
| section entitled ``GNU Free Documentation License''.--> | ||||
| <meta http-equiv="Content-Style-Type" content="text/css"> | ||||
| <style type="text/css"><!-- | ||||
|   pre.display { font-family:inherit } | ||||
|   pre.format  { font-family:inherit } | ||||
|   pre.smalldisplay { font-family:inherit; font-size:smaller } | ||||
|   pre.smallformat  { font-family:inherit; font-size:smaller } | ||||
|   pre.smallexample { font-size:smaller } | ||||
|   pre.smalllisp    { font-size:smaller } | ||||
|   span.sc { font-variant:small-caps } | ||||
|   span.roman { font-family: serif; font-weight: normal; }  | ||||
| --></style> | ||||
| </head> | ||||
| <body> | ||||
| <div class="node"> | ||||
| <p> | ||||
| <a name="BFD"></a>Next: <a rel="next" accesskey="n" href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a>, | ||||
| Previous: <a rel="previous" accesskey="p" href="Machine-Dependent.html#Machine-Dependent">Machine Dependent</a>, | ||||
| Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a> | ||||
| <hr><br> | ||||
| </div> | ||||
| 
 | ||||
| <h2 class="chapter">5 BFD</h2> | ||||
| 
 | ||||
| <p><a name="index-back-end-629"></a><a name="index-object-file-management-630"></a><a name="index-object-formats-available-631"></a><a name="index-objdump-_002di-632"></a>The linker accesses object and archive files using the BFD libraries.  | ||||
| These libraries allow the linker to use the same routines to operate on | ||||
| object files whatever the object file format.  A different object file | ||||
| format can be supported simply by creating a new BFD back end and adding | ||||
| it to the library.  To conserve runtime memory, however, the linker and | ||||
| associated tools are usually configured to support only a subset of the | ||||
| object file formats available.  You can use <code>objdump -i</code> | ||||
| (see <a href="../binutils/objdump.html#objdump">objdump (The GNU Binary Utilities)</a>) to | ||||
| list all the formats available for your configuration. | ||||
| 
 | ||||
|    <p><a name="index-BFD-requirements-633"></a><a name="index-requirements-for-BFD-634"></a>As with most implementations, BFD is a compromise between | ||||
| several conflicting requirements. The major factor influencing | ||||
| BFD design was efficiency: any time used converting between | ||||
| formats is time which would not have been spent had BFD not | ||||
| been involved. This is partly offset by abstraction payback; since | ||||
| BFD simplifies applications and back ends, more time and care | ||||
| may be spent optimizing algorithms for a greater speed. | ||||
| 
 | ||||
|    <p>One minor artifact of the BFD solution which you should bear in | ||||
| mind is the potential for information loss.  There are two places where | ||||
| useful information can be lost using the BFD mechanism: during | ||||
| conversion and during output. See <a href="BFD-information-loss.html#BFD-information-loss">BFD information loss</a>. | ||||
| 
 | ||||
| <ul class="menu"> | ||||
| <li><a accesskey="1" href="BFD-outline.html#BFD-outline">BFD outline</a>:                  How it works: an outline of BFD | ||||
| </ul> | ||||
| 
 | ||||
|    </body></html> | ||||
| 
 | ||||
		Reference in a new issue