[Bug ld/17488] [2.25 regression] ld segfaults building slof (Slimline Open Firmware -- QEMU PowerPC version)

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17488

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, binutils-2_25-branch has been updated
       via  16bfc7bb18b272d5a4e40ee37ced21e4b9a8fbb4 (commit)
      from  986b34e134011175be26b4504ba8a4f8e38de2bf (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=16bfc7bb18b272d5a4e40ee37ced21e4b9a8fbb4

commit 16bfc7bb18b272d5a4e40ee37ced21e4b9a8fbb4
Author: Alan Modra <address@hidden>
Date:   Thu Oct 16 09:38:09 2014 +1030

    PR17488, powerpc64-linux-ld segfault

    For binary ouput, we don't have an ELF bfd output so can't access
    elf_elfheader.  The elf64-ppc.c changes are really just a tidy,
    triggered by looking at all places where the abiversion bits are
    accessed.

    bfd/
        * elf64-ppc.c (ppc64_elf_before_check_relocs): Do .opd processing
        even when output is not ppc64 ELF.  Remove redundant tests on
        type of input bfd.
    ld/
        PR 17488
        * emultempl/ppc64elf.em (gld${EMULATION_NAME}_finish): Don't attempt
        to access ELF header e_flags when not ppc64 ELF output.

-----------------------------------------------------------------------

Summary of changes:
 bfd/ChangeLog            |    5 ++
 bfd/elf64-ppc.c          |  126 ++++++++++++++++++++++------------------------
 ld/ChangeLog             |    8 +++
 ld/emultempl/ppc64elf.em |    3 +-
 4 files changed, 76 insertions(+), 66 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.