ARM Compiler toolchain Using the Linker - ARM Information Center

6.3.1 See also
(incl. Generated)
Getting information about images
armlink might generate image contents, for example, interworking veneers, and
input sections such as region tables. If the Object Totals row includes this type of
data, it is shown in this row.
In the example, there are 19 bytes of RO data in total, of which 16 bytes is
linker-generated RO data.
Library Totals
Shows how many bytes are occupied by library members that have been extracted
and added to the image as individual objects.
(incl. Padding)
armlink inserts padding, if required, to force section alignment. If the Object
Totals row includes this type of data, it is shown in the associated (incl. Padding)
row. Similarly, if the Library Totals row includes this type of data, it is shown in
its associated row.
In the example, there are 19 bytes of RO data in the object total, of which 3 bytes
is linker-generated padding, and 805 bytes of RO data in the library total, with 6
bytes of padding.
Grand Totals
Shows the true size of the image. In the example, there are 10200 bytes of ZI data
(in Object Totals) and 300 of ZI data (in Library Totals) giving a total of 10500
bytes.
ELF Image Totals
If you are using RW data compression (the default) to optimize ROM size, the
size of the final image changes and this is reflected in the output from --info.
Compare the number of bytes under Grand Totals and ELF Image Totals to see the
effect of compression.
In the example, RW data compression is not enabled. If data is compressed, the
RW value changes.
ROM Totals
Shows the minimum size of ROM required to contain the image. This does not
include ZI data and debug information which is not stored in the ROM.
Concepts
• Linker options for getting information about images on page 6-2.
Reference
Linker Reference:
• --info=topic[,topic,...] on page 2-80.
ARM DUI 0474C Copyright © 2010-2011 ARM. All rights reserved. 6-5
ID080411 Non-Confidential