|
|||||||||||
Technical Support On-Line Manuals Linker User Guide ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Steering file format
6.6.3 Steering file formatEach command in a steering file must be on a separate line. A steering file has the following format:
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 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 | ||||||||||
|
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.