ARM Compiler toolchain Using the Linker - ARM Information Center

6.3 Example of using the --info linker option
To display the component sizes when linking enter:
armlink --info sizes ...
Getting information about images
Here, sizes gives a list of the Code and Data sizes for each input object and library member in
the image. Using this option implies --info sizes,totals.
The following example shows the output in tabular format with the totals separated out for easy
reading:
Code (inc. data) RO Data RW Data ZI Data Debug
Example 6-1 Image component size information
3712 1580 19 44 10200 7436 Object Totals
0 0 16 0 0 0 (incl. Generated)
0 0 3 0 0 0 (incl. Padding)
21376 648 805 4 300 10216 Library Totals
0 0 6 0 0 0 (incl. Padding)
===============================================================================
Code (inc. data) RO Data RW Data ZI Data Debug
25088 2228 824 48 10500 17652 Grand Totals
25088 2228 824 48 10500 17652 ELF Image Totals
25088 2228 824 48 0 0 ROM Totals
===============================================================================
Total RO Size (Code + RO Data) 25912 ( 25.30kB)
Total RW Size (RW Data + ZI Data) 10548 ( 10.30kB)
Total ROM Size (Code + RO Data + RW Data) 25960 ( 25.35kB)
In this example:
Code (inc. Data)
Shows how many bytes are occupied by code. In this image, there are 3712 bytes
of code. This includes 1580 bytes of inline data (inc. data), for example, literal
pools, and short strings.
RO Data Shows how many bytes are occupied by read-only data. This is in addition to the
inline data included in the Code (inc. data) column.
RW Data Shows how many bytes are occupied by read-write data.
ZI Data Shows how many bytes are occupied by zero-initialized data.
Debug Shows how many bytes are occupied by debug data, for example, debug input
sections and the symbol and string table.
Object Totals
Shows how many bytes are occupied by objects linked together to generate the
image.
ARM DUI 0474C Copyright © 2010-2011 ARM. All rights reserved. 6-4
ID080411 Non-Confidential