|
|||
| Products Download Events Support Videos | |||
Technical Support
On-Line Manuals
Compiler User Guide
Conventions and Feedback
Overview of the Compiler
Getting Started with the Compiler
Compiler command-line syntax
Compiler command-line options listed by group
Default compiler behavior
Order of compiler command-line options
Using stdin to input source code to the compiler
Directing output to stdout
Filename suffixes recognized by the compiler
Compiler output files
Factors influencing how the compiler searches for
Compiler command-line options and search paths
Compiler search rules and the current place
The ARMCCnINC environment variable
Code compatibility between separately compiled and
Linker feedback during compilation
Unused function code
Minimizing code size by eliminating unused functio
Minimizing code size by reducing compilation requi
Compilation build time
How to minimize compilation build time
Minimizing compilation build time with a single ar
Effect of --multifile on compilation build time
Minimizing compilation build time with parallel ma
Compilation build time and operating system choice
Compiler Features
Compiler Coding Practices
Compiler Diagnostic Messages
Using the Inline and Embedded Assemblers of the AR
Compiler User Guide
Minimizing code size by eliminating unused functions during compilation
| |||
| Home > Getting Started with the Compiler > Minimizing code size by eliminating unused functions during compilation | |||
To eliminate unused functions from your object files:
Compile your source code.
Use the linker option
--feedback=to create a feedback file. By default, the type of feedback generated is for the elimination of unused functions.filenameRe-compile using the compiler option
--feedback=to feed the feedback file to the compiler.filename
The compiler uses the feedback file generated by the linker to compile the source code in a way that enables the linker to subsequently discard the unused functions.
Note
To obtain maximum benefit from linker feedback, do a full compile and link at least twice. A single compile and link using feedback from a previous build is normally sufficient to obtain some benefit.
You can specify the --feedback= option
even when no feedback file exists. This enables you to use the same
build or make file regardless of whether a feedback file exists,
for example:filename
armcc -c --feedback=unused.txt test.c -o test.o armlink --feedback=unused.txt test.o -o test.axf
The first time you build the application, it compiles normally but the compiler warns you that it cannot read the specified feedback file because it does not exist. The link command then creates the feedback file and builds the image. Each subsequent compilation step uses the feedback file from the previous link step to remove any unused functions that are identified.
See also- Tasks
Using the Linker:
- Concepts
- Reference
| Copyright © 2007-2008, 2011-2012 ARM. All rights reserved. | ARM DUI 0375D |
| Non-Confidential | ID062912 |
 PDF version | |
| Home > Getting Started with the Compiler > Minimizing code size by eliminating unused functions during compilation |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
|
 |
|||
