summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-readobj
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2019-04-15 10:57:44 +0000
committerMartin Storsjo <martin@martin.st>2019-04-15 10:57:44 +0000
commitcdf126ebec185d135dfb99cb907cf4f40583e3dc (patch)
tree26c851b7a608cb5063b75169eecd748a988b1820 /llvm/tools/llvm-readobj
parent7844031d460403596f151c30068d7fe062d92b37 (diff)
downloadbcm5719-llvm-cdf126ebec185d135dfb99cb907cf4f40583e3dc.tar.gz
bcm5719-llvm-cdf126ebec185d135dfb99cb907cf4f40583e3dc.zip
[COFF] Link crtend.o as the last object file
When faced with command line options such as "crtbegin.o appmain.o -lsomelib crtend.o", GNU ld pulls in all necessary object files from somelib before proceeding to crtend.o. LLD operates differently, only loading object files from any referenced static libraries after processing all input object files. This uses a similar hack as in the ELF linker. Here, it moves crtend.o to the end of the vector of object files. This makes sure that terminator chunks for sections such as .eh_frame gets ordered last, fixing DWARF exception handling for libgcc and gcc's crtend.o. Differential Revision: https://reviews.llvm.org/D60628 llvm-svn: 358394
Diffstat (limited to 'llvm/tools/llvm-readobj')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud