After you have created the output file, all data sections from the input files are copied to the new image. Any relocations specified by the input files are applied to the output image. Any additional relocation information that must be generated is also written to the new image.
Relocation processing is normally uneventful, although error conditions might arise that are accompanied by specific error messages. Two conditions are worth more discussion. The first condition involves text relocations that result from position-dependent code. This condition is covered in more detail in Position-Independent Code. The second condition can arise from displacement relocations, which is described more fully in the next section.
Error conditions might occur if displacement relocations are applied to a data item, which can be used in a copy relocation. The details of copy relocations are covered in Copy Relocations.
A displacement relocation remains valid when both the relocated offset and the relocation target remain separated by the same displacement. A copy relocation is where a global data item within a shared object is copied to the .bss of a dynamic executable. This copy preserves the executable's read-only text segment. If the copied data has a displacement relocation applied to the data, or an external relocation is a displacement into the copied data, the displacement relocation becomes invalidated.
Two areas of validation attempt to catch displacement relocation problems.
The first occurs when generating a shared object. Any potential copy relocatable data items that can be problematic if the copied data is involved in a displacement relocation are flagged. During construction of a shared object, the link-editor has no knowledge of what external references might be made to a data item. Thus, all that can be flagged are potential problems.
The second occurs when generating a dynamic executable. The creation of a copy relocation whose data is known to be involved in a displacement relocation is flagged.
However, displacement relocations applied to a shared object might be completed during the shared objects creation at link-edit time. These displacement relocations might not have been flagged. The link-edit of a dynamic executable that references an unflagged shared object has no knowledge of a displacement being in effect in any copy-relocated data.
To help diagnose these problem areas, the link-editor indicates the displacement relocation use of a dynamic object with one or more dynamic DT_FLAGS_1 flags, as shown in Figure 48, Table 48, ELF Dynamic Flags, DT_FLAGS_1. In addition, the link-editor's –z verbose option can be used to display suspicious relocations.
For example, say you create a shared object with a global data item, bar, to which a displacement relocation is applied. This item could be copy-relocated if referenced from a dynamic executable. The link-editor warns of this condition.
$ cc -G -o libfoo.so.1 -z verbose -K pic foo.o ld: warning: relocation warning: R_SPARC_DISP32: file foo.o: symbol foo: \ displacement relocation to be applied to the symbol bar: at 0x194: \ displacement relocation will be visible in output image
If you now create an application that references the data item bar, a copy relocation is created. This copy results in the displacement relocation being invalidated. Because the link-editor can explicitly discover this situation, an error message is generated regardless of the use of the –z verbose option.
$ cc -o prog prog.o -L. -lfoo ld: warning: relocation error: R_SPARC_DISP32: file foo.so: symbol foo: \ displacement relocation applied to the symbol bar at: 0x194: \ the symbol bar is a copy relocated symbol
These error conditions can be avoided by ensuring that the symbol definition being relocated (offset) and the symbol target of the relocation are both local. Use static definitions or the link-editor's scoping technology. See Reducing Symbol Scope. Relocation problems of this type can be avoided by accessing data within shared objects by using functional interfaces.