|
|||
| Products Download Events Support Videos | |||
Technical Support
On-Line Manuals
Linker User Guide
Conventions and feedback
Overview of the linker
Linking models supported by armlink
Image structure and generation
Using linker optimizations
Getting information about images
Accessing and managing symbols with armlink
About mapping symbols
Accessing linker-defined symbols
Region-related symbols
Image$$ execution region symbols
Load$$ execution region symbols
Load$$LR$$ load region symbols
Region name values when not scatter-loading
Using scatter files
Importing linker-defined symbols in C and C++
Importing linker-defined symbols in ARM assembler
Section-related symbols
Image symbols
Input section symbols
Accessing symbols in another image
Creating a symdefs file
Outputting a subset of the global symbols
Reading a symdefs file
Symdefs file format
What is a steering file?
Specifying steering files on the linker command-li
Steering file command summary
Steering file format
Hiding and renaming global symbols with a steering
Using $Super$$ and $Sub$$ to patch symbol definiti
Using scatter files
About mapping symbols
| |||
| Home > Accessing and managing symbols with armlink > About mapping symbols | |||
Mapping symbols are generated by armcc and armasm to identify inline transitions between:
code and data at literal pool boundaries
ARM code and Thumb code, such as ARM/Thumb interworking veneers.
The mapping symbols are:
- $a
start of a sequence of ARM instructions
- $t
start of a sequence of Thumb instructions
- $t.x
start of a sequence of ThumbEE instructions
- $d
start of a sequence of data items, such as a literal pool.
armlink generates the $d.realdata mapping
symbol to communicate to fromelf that the data
is from a non-executable section. Therefore, the code and data sizes
output by fromelf -z are the same as the output
from armlink --info sizes, for example:
Code (inc. data) RO Data
x y z
In this example, the y is marked with $d,
and RO Data is marked with $d.realdata.
Note
Symbols beginning with the characters $v are
mapping symbols related to VFP and might be output when building
for a target with VFP. Avoid using symbols beginning with $v in
your source code.
See also- Concepts
Using the Assembler:
- Reference
Linker Reference:
Using the fromelf Image Converter:
- Other information
| Copyright © 2007-2008, 2011-2012 ARM. All rights reserved. | ARM DUI 0377D |
| Non-Confidential | ID062912 |
 PDF version | |
| Home > Accessing and managing symbols with armlink > About mapping symbols |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
|
 |
|||
