summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/InitPreprocessor.cpp
diff options
context:
space:
mode:
authorPeter Collingbourne <peter@pcc.me.uk>2018-05-30 19:30:39 +0000
committerPeter Collingbourne <peter@pcc.me.uk>2018-05-30 19:30:39 +0000
commit1651ac13be81bae08365dda486263a1fec04f2d2 (patch)
tree37ed80abd21e2877b12c6b658e7700c8b8c59d1e /clang/lib/Frontend/InitPreprocessor.cpp
parent5e9f459c6260d84a93f1c52c682474025ca060cb (diff)
downloadbcm5719-llvm-1651ac13be81bae08365dda486263a1fec04f2d2.tar.gz
bcm5719-llvm-1651ac13be81bae08365dda486263a1fec04f2d2.zip
llvm-objcopy: Set sh_link to 0 on unrecognized symtab-linked sections.
Per discussion on the generic-abi mailing list: https://groups.google.com/forum/#!topic/generic-abi/MPr8TVtnVn4 An object file manipulation tool must either write out a symbol table with the same number of entries as the original symbol table and in the same order, or if this is impossible, refuse to operate on the object file if it has unrecognized sections that are linked to the symtab section. However, existing tools (namely GNU strip, GNU objcopy and ld.{bfd,gold,lld} -r) do not comply with this at present: they change symbol table indexes and set sh_link to 0 on the unrecognized symtab-linked sections. We intend to use the latter as a (temporary) signal that a tool has operated on a proposed new symtab-linked section and invalidated the symbol table indexes. However, llvm-objcopy currently keeps sh_link pointing to the new symtab section. This patch changes llvm-objcopy to set sh_link to 0 to match the behaviour of the other tools. Differential Revision: https://reviews.llvm.org/D47404 llvm-svn: 333581
Diffstat (limited to 'clang/lib/Frontend/InitPreprocessor.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud