Deadstripping

As the linker combines object files into one executable file, it recognizes portions of executable code that execution cannot possibly reach. Deadstripping is removing such unreachable object code - that is, excluding these portions in the executable file. The CodeWarrior linker performs this deadstripping on a per-function basis.

The CodeWarrior linker deadstrips unused code and data from only object files that a CodeWarrior compiler generates. The linker never deadstrips assembler-relocatable files, or object files from a different compiler.

Deadstripping is particularly useful for C++ programs or for linking to large, general-purpose libraries. Libraries (archives) built with the CodeWarrior compiler only contribute the used objects to the linked program. If a library has assembly or other compiler built files, only those files that have at least one referenced object contribute to the linked program. The linker always ignores unreferenced object files.

Well-constructed projects probably do not contain unused data or code. Accordingly, you can reduce the time linking takes by disabling deadstripping:

• To disable deadstripping for particular symbols, enter the symbol names in the Force Active Symbols text box of the ColdFire Linker Settings Panel.
• To disable deadstripping for individual sections of the linker command file, use the KEEP_SECTION() directive. As code does not directly reference interrupt-vector tables, a common use for this directive is disabling deadstripping for these interrupt-vector tables. The subsection Closure Segments provides additional information about the KEEP_SECTION() directive.
  Note: To deadstrip files from standalone assembler, you must make each assembly functions start its own section (for example, a new .text directive before functions) and using an appropriate directive.