summaryrefslogtreecommitdiff
path: root/gnu/usr.bin/binutils/ld/ldmain.c
AgeCommit message (Collapse)Author
2004-11-02Merge conflicts, bringing our changes back in:Miod Vallat
- extra $(SHELL) and sugar for make (so that files not mode +x still work) - safer temp file handling - our W^X binary layout changes in ld - OpenBSD policy for library file selection in ld - arm and m88k changes which were not merged in time for official 2.15 - bfd core file handling - a couple typos New for 2.15: - ld(1) and as(1) manpages now generated at build time - binutils/stabs.c reverted to use our in-tree libiberty for now - we still use our VIA C3 crypto code over stock binutils, as it recognizes more instructions - new emulations for OpenBSD on mips64 machines, to help OpenBSD/sgi - relaxed %f# handling in gas on OpenBSD/sparc64 (same as was in 2.14) Tested on all platforms by various people; special thanks to sturm@ and otto@.
2004-05-17Resolve merge conflicts, adjust method of W^X handing (.sh files)Dale Rahn
remove testsuites (not useable) remove mmalloc (not part of new binutils).
2003-01-17This is a project to modify executables so that they do not have anyDale Rahn
executable regions which are writable. If a section of an executable is writable and executable, it is much easier for errant code to modify the executable's behavior. Two current areas in shared library environments which have this critical problem are the GOT (Global Offset Table) and PLT (Procedure Linkage Table). The PLT is required to be executable and both GOT and PLT are writable on most architectures. On most ELF architecture machines this would cause shared libraries to have data and BSS marked as executable. Padding to the linker script for programs and shared libraries/objects to isolate the GOT and PLT into their own load sections in the executables. This allows only the text(readonly) region and the PLT region to be marked executable with the normal data and BSS not marked as executable. The PLT region is still marked executable on most architectures because the PLT lives in the "data" or "BSS" regions and the dynamic loader will need to modify it. Since the GOT and PLT should only ever be written by the dynamic linker, it will be modified to mprotect those regions so that they are not writable during normal execution. If the dynamic linker needs to modify the regions later, (eg for lazy binding), it will mprotect the region, make the necessary changes, and mprotect it back. Since it is possible to receive a signal which would interrupt the program flow and perhaps cause the dynamic linker to modify the same (or nearby) PLT references, it is now necessary for signals to be blocked for the duration of the mprotect.
2002-05-13resolve conflicts.Federico G. Schwindt
2000-09-12Help stupid cvs fixing basic conflicts.Marc Espie
1996-11-23Merge to Cygnus 961112 + add some support (not ready) for shared libsNiklas Hallqvist
1996-09-04Merge the Cygnus 960904 sourcesNiklas Hallqvist
1996-06-10Bring Cygnus versions into the trunk, keeping our local patchesNiklas Hallqvist
1996-01-08Initial GNU binutils 2.6 importNiklas Hallqvist