diff options
| author | Alan Modra <amodra@gmail.com> | 2017-10-30 10:20:29 +1030 |
|---|---|---|
| committer | Alan Modra <amodra@gmail.com> | 2017-10-30 11:03:50 +1030 |
| commit | 81742b83e9f25895eaaf3a07ac1651a4e9a68251 (patch) | |
| tree | ce6ef2cdab6327ca8f8a795454c4d37f08a00579 /gdb/cli/cli-script.c | |
| parent | d336fa6d820f50235c271ea327fadbf4ff6e1edd (diff) | |
| download | binutils-81742b83e9f25895eaaf3a07ac1651a4e9a68251.zip binutils-81742b83e9f25895eaaf3a07ac1651a4e9a68251.tar.gz binutils-81742b83e9f25895eaaf3a07ac1651a4e9a68251.tar.bz2 | |
relocs_compatible test for gc-sections
I noticed when looking at pr22300 that before calling check_relocs we
have an elf_object_id test (added for pr11933) as well as the
relocs_compatible test. I believe backend gc_mark_hook and
gc_sweep_hook ought to be protected similarly from being confused by
unexpected relocations (for example, both elf64-ppc.c and elf32-ppc.c
use _bfd_elf_relocs_compatible, so I think it would be possible for
the ppc64 gc_mark_hook to be presented with a ppc32 relocatable
object).
* elflink.c (elf_gc_sweep): Test elf_object_id in addition to
relocs_compatible.
(bfd_elf_gc_sections): Likewise.
Diffstat (limited to 'gdb/cli/cli-script.c')
0 files changed, 0 insertions, 0 deletions