|
||
| Products Download Events Support Videos | ||
Technical Support
On-Line Manuals
Linker User Guide
Preface
Overview of the Linker
Linking Models Supported by armlink
Image Structure and Generation
Linker Optimization Features
Getting Image Details
Accessing and Managing Symbols with armlink
About mapping symbols
Linker-defined symbols
Region-related symbols
Types of region-related symbols
Image$$ execution region symbols
Load$$ execution region symbols
Load$$LR$$ load region symbols
Region name values when not scatter-loading
Linker defined symbols and scatter files
Methods of importing linker-defined symbols in C a
Methods of importing linker-defined symbols in ARM
Section-related symbols
Types of section-related symbols
Image symbols
Input section symbols
Access symbols in another image
Creating a symdefs file
Outputting a subset of the global symbols
Reading a symdefs file
Symdefs file format
Edit the symbol tables with a steering file
Specifying steering files on the linker command-li
Steering file command summary
Steering file format
Hide and rename global symbols with a steering fil
Use of $Super$$ and $Sub$$ to patch symbol definit
Scatter-loading Features
Scatter File Syntax
Linker Command-line Options
Linker Steering File Command Reference
Via File Syntax
Steering file format
| Non-Confidential |  PDF version | ARM DUI0377H | ||
| ||||
| Home > Accessing and Managing Symbols with armlink > Edit the symbol tables with a steering file > Steering file format | ||||
6.6.3 Steering file format
Each command in a steering file must be on a separate line.
A steering file has the following format:
- Lines with a semicolon (
;) or hash (#) character as the first non-whitespace character are interpreted as comments. A comment is treated as a blank line. - Blank lines are ignored.
- Each non-blank, non-comment line is either a command, or part of a command that is split over consecutive non-blank lines.
- Command lines that end with a comma (
,) as the last non-whitespace character are continued on the next non-blank line.
Each command line consists of a command, followed by one or more comma-separated operand
groups. Each operand group comprises either one or two operands, depending on the command.
The command is applied to each operand group in the command. The following rules apply:
- Commands are case-insensitive, but are conventionally shown in uppercase.
- Operands are case-sensitive because they must be matched against case-sensitive symbol names. You can use wildcard characters in operands.
Commands are applied to global symbols only. Other symbols, such as local symbols, are not
affected.
The following example shows a sample steering file:
; Import my_func1 as func1
IMPORT my_func1 AS func1
# Rename a very long function name to a shorter name
RENAME a_very_long_function_name AS,
short_func_name
| Non-Confidential | PDF version | ARM DUI0377H |
| Copyright © 2007, 2008, 2011, 2012, 2014-2016 ARM. All rights reserved. |
| Home > Accessing and Managing Symbols with armlink > Edit the symbol tables with a steering file > Steering file format |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
 |
||||