Difference between revisions of "Symbol"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
int a=5; | int a=5; | ||
| − | In the compiled code, the name of the variable is insignificant -- the object code will access the relevant memory location by address at the [[Machine Language|machine code]] level. | + | In the compiled code, the name of the variable is insignificant -- the object code will access the relevant memory location by address, or the relevant register, at the [[Machine Language|machine code]] level. |
Symbolic information is generally lost during compilation, unless it is specifically preserved by the compiler. Most C compilers use the <code>-g</code> option to request that symbol information be attached to the binary for debugging purposes; a [[Debugger|debugger]] or [[Disassembler|disassembler]] can use this information to convert addresses and other numeric information to a symbolic representation. (Debug information may also include code-address-to-source-line-number cross reference data so that errors, code listings, and single-step operations can display or refer to the relevant source code). | Symbolic information is generally lost during compilation, unless it is specifically preserved by the compiler. Most C compilers use the <code>-g</code> option to request that symbol information be attached to the binary for debugging purposes; a [[Debugger|debugger]] or [[Disassembler|disassembler]] can use this information to convert addresses and other numeric information to a symbolic representation. (Debug information may also include code-address-to-source-line-number cross reference data so that errors, code listings, and single-step operations can display or refer to the relevant source code). | ||
| − | In order to reduce the size of distributed binaries, symbolic debug data may be separated from the binary and placed in another file. This can be accessed from a local file, or a ''symbol server'' set up for this purpose. | + | In order to reduce the size of distributed binaries, symbolic debug data may be separated from the binary and placed in another file. This can be accessed from a local file, or a ''symbol server'' set up for this purpose. Alternately, it may be removed from the binary and discarded. The tool that performs this function on most Linux and Unix systems is called <code>strip</code>. |
== Reserved Names == | == Reserved Names == | ||
Many tools (such as [[Assembler|assemblers]]) have ''reserved names'' -- names which cannot be used for user-defined symbols because they conflict with pre-defined or internal symbols or create ambiguity in the source code. For example, in aarch64 gas assembly syntax, you cannot use x0 as a constant name, because it conflicts with the register name. | Many tools (such as [[Assembler|assemblers]]) have ''reserved names'' -- names which cannot be used for user-defined symbols because they conflict with pre-defined or internal symbols or create ambiguity in the source code. For example, in aarch64 gas assembly syntax, you cannot use x0 as a constant name, because it conflicts with the register name. | ||
Latest revision as of 16:23, 11 September 2019
A symbol is a name for a variable, address, register, or instruction.
For example, the symbol "a" is used in this C code:
int a=5;
In the compiled code, the name of the variable is insignificant -- the object code will access the relevant memory location by address, or the relevant register, at the machine code level.
Symbolic information is generally lost during compilation, unless it is specifically preserved by the compiler. Most C compilers use the -g option to request that symbol information be attached to the binary for debugging purposes; a debugger or disassembler can use this information to convert addresses and other numeric information to a symbolic representation. (Debug information may also include code-address-to-source-line-number cross reference data so that errors, code listings, and single-step operations can display or refer to the relevant source code).
In order to reduce the size of distributed binaries, symbolic debug data may be separated from the binary and placed in another file. This can be accessed from a local file, or a symbol server set up for this purpose. Alternately, it may be removed from the binary and discarded. The tool that performs this function on most Linux and Unix systems is called strip.
Reserved Names
Many tools (such as assemblers) have reserved names -- names which cannot be used for user-defined symbols because they conflict with pre-defined or internal symbols or create ambiguity in the source code. For example, in aarch64 gas assembly syntax, you cannot use x0 as a constant name, because it conflicts with the register name.
