Process for reducing the size of an executable

by

General list:

  • Make sure that you have the compiler and linker debug options disabled
  • Compile and link with all size options turned on (-Os in gcc)
  • Run strip on the executable
  • Generate a map file and check your function sizes. You can either get your linker to generate your map file (-M when using ld), or you can use objdump on the final executable (note that this will only work on an unstripped executable!) This won’t actually fix the problem, but it will let you know of the worst offenders.
  • Use nm to investigate the symbols that are called from each of your object files. This should help in finding who’s calling functions that you don’t want called.

In the original question was a sub-question about including only relevant functions. gcc will include all functions within every object file that is used. To put that another way, if you have an object file that contains 10 functions, all 10 functions are included in your executable even if one 1 is actually called.

The standard libraries (eg. libc) will split functions into many separate object files, which are then archived. The executable is then linked against the archive.
By splitting into many object files the linker is able to include only the functions that are actually called. (this assumes that you’re statically linking)

There is no reason why you can’t do the same trick. Of course, you could argue that if the functions aren’t called the you can probably remove them yourself.

If you’re statically linking against other libraries you can run the tools listed above over them too to make sure that they’re following similar rules.

More Related Contents:

  1. Looking for an efficient integer square root algorithm for ARM Thumb2
  2. Cycle counter on ARM Cortex M4 (or M3)?
  3. Simple serial point-to-point communication protocol
  4. Explaination of ARM (especifically mobile) Peripherals Addressing and Bus architecture?
  5. How do you design a serial command protocol for an embedded system? [closed]
  6. Why do we need a bootloader in an embedded device?
  7. STM32 how to get last reset status
  8. The mouse pointer manipulating code [closed]
  9. Access of register STM32 CAN communication
  10. Understanding Linux /proc/pid/maps or /proc/self/maps
  11. How to access physical addresses from user space in Linux?
  12. How to determine maximum stack usage?
  13. ARM compilation error, VFP registers used by executable, not object file
  14. How does native android code written for ARM run on x86?
  15. Can _start be the thumb function?
  16. Why use armeabi-v7a code over armeabi code?
  17. How to run a single line of assembly, then see [R1] and condition flags
  18. TrustZone monitor mode and IFAR, IFSR, DFAR, DFSR
  19. How do you implement a class in C? [closed]
  20. How instructions are differentiated from data?
  21. How can I select a static library to be linked while ARM cross compiling?
  22. Arm Neon Intrinsics vs hand assembly
  23. High delay in RS232 communication on a PXA270
  24. duplicate symbols for architecture armv7
  25. using serial port RS-232 in android?
  26. Fixed address variable in C
  27. Explicitly accessing banked registers on ARM
  28. Convert ASM to C (not reverse engineer)
  29. Android emulator system images and AMD processor
  30. Fast Division on GCC/ARM

Leave a Comment