[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/2404] Linker failed to handle symbols with mismatched types.
From: |
cvs-commit at gcc dot gnu.org |
Subject: |
[Bug ld/2404] Linker failed to handle symbols with mismatched types. |
Date: |
Tue, 21 Jan 2014 13:35:58 +0000 |
http://sourceware.org/bugzilla/show_bug.cgi?id=2404
--- Comment #4 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, master has been updated
via 22ef172a21663abb477d72284b4d59c8eabcbb82 (commit)
from 48ded086b6d25529dd336d74b73788d3cf87cfda (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=22ef172a21663abb477d72284b4d59c8eabcbb82
commit 22ef172a21663abb477d72284b4d59c8eabcbb82
Author: H.J. Lu <address@hidden>
Date: Tue Jan 21 05:33:48 2014 -0800
Don't check shared/export_dynamic/ref_dynamic for type mismatch
There is nothing linker can do when a type mismatched default definition
are made dynamic by info->shared, info->export_dynamic or h->ref_dynamic.
But we do want to avoid exporting it when building PIE. Let's remove
those checks.
bfd/
PR ld/2404
* elflink.c (_bfd_elf_merge_symbol): Don't check info->shared,
info->export_dynamic, nor !h->ref_dynamic for type mismatch when
adding the default version.
ld/testsuite/
PR ld/2404
* ld-elf/shared.exp: Add a PIE test for PR ld/2404.
-----------------------------------------------------------------------
Summary of changes:
bfd/ChangeLog | 7 +++++++
bfd/elflink.c | 3 ---
ld/testsuite/ChangeLog | 5 +++++
ld/testsuite/ld-elf/shared.exp | 26 ++++++++++++++++++++++++++
4 files changed, 38 insertions(+), 3 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.