2

This would probably be achieved in the linking stage of the GCC compiler? But are there any specific references on this stage?

Also, is there a tool that can perform code size reduction by knowing which pieces of code isn't called?

David d C e Freitas
  • 7,481
  • 4
  • 58
  • 67

1 Answers1

1

You can compress the final size of your executable using tools like:

  • UPX - Ultimate Packet for eXecutables (Great tool for shrinking any object code file e.g. .exe, .dll, .elf)

Here are a few references regarding stripping code during the gcc/ld compilation or linking phases:

So I imagine this has to be done on a code level and can't be done on compiled code in the way that Java bytecode can be worked with...

Community
  • 1
  • 1
David d C e Freitas
  • 7,481
  • 4
  • 58
  • 67
  • For the obfusication aspect of ProGuard take a look at the answers to this related question: http://stackoverflow.com/questions/1025494/obfuscating-c-c-code – Rian Sanderson Nov 16 '11 at 21:40