03322b9583
__start_SECNAME and __stop_SECNAME symbols are automatically generated by ld for orphan sections, i.e. those not explicitely referenced by a linker script. The symbols are supposed to be placed correspondingly at the start and the end of the section in output file. In some cases __start_SECNAME may be placed at the address after the end of the previous section (if any) and before the start the section. This happens when following conditions are met: 1. the orphan section is found in more than one input file 2. the orphan section has different alignment requirements across input files 3. the first instance of the section encountered doesn't have the greatest alignment requirement In these conditions resulting output section will be placed at address after the end of the previous section aligned to the greatest alignment requirement in the inputs, but __start_SECNAME will be placed at address after the end of the previous section aligned to the alignment requirement of the first input in which the section is encountered. See commit message of r196118 for a concrete example of problems caused by this bug. The fix is to place __start_SECNAME inside the section and use ABSOLUTE directive, rather than placing __start_SECNAME outside the section and trying to guess address alignment. This fix is in line with upstream binutils change/fix made between versions 2.19 and 2.20 in revision of 1.307 ldlang.c. MFC after: 3 weeks |
||
|---|---|---|
| .. | ||
| alphaelf.em | ||
| armcoff.em | ||
| armelf_oabi.em | ||
| armelf.em | ||
| astring.sed | ||
| elf32.em | ||
| generic.em | ||
| ia64elf.em | ||
| linux.em | ||
| mipsecoff.em | ||
| mipself.em | ||
| needrelax.em | ||
| netbsd.em | ||
| ostring.sed | ||
| pe.em | ||
| ppc32elf.em | ||
| ppc64elf.em | ||
| README | ||
| sunos.em | ||
| ticoff.em | ||
| vanilla.em | ||
The files in this directory are sourced by genscripts.sh, after setting some variables to substitute in, to produce C source files that contain jump tables for each emulation.