bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/29512] ld non-canon ref to canon protected function check breaks


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/29512] ld non-canon ref to canon protected function check breaks Solaris/x86
Date: Thu, 25 Aug 2022 16:12:56 +0000

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

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2c43d202aefb2b6f202a44bbb8a0baf251aae845

commit 2c43d202aefb2b6f202a44bbb8a0baf251aae845
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Aug 22 10:26:17 2022 -0700

    x86: Ignore protected visibility in shared libraries on Solaris

    On x86, the PLT entry in executable may be used as function address for
    functions in shared libraries.  If functions are protected, the function
    address used in executable can be different from the function address
    used in shared library.  This will lead to incorrect run-time behavior
    if function pointer equality is needed.  By default, x86 linker issues
    an error in this case.

    On Solaris, linker issued an error for

    struct tm *tb = (kind == CPP_time_kind::FIXED ? gmtime : localtime) (&tt);

    where gmtime is a protected function in libc.so.  Use gmtime's PLT entry
    in executable as function address is safe since function pointer equality
    isn't needed.  Ignore protected visibility in shared libraries on Solaris
    to disable linker error.  If function pointer equality is needed, linker
    will silently generate executable with incorrect run-time behavior on
    Solaris.

            PR ld/29512
            * elf32-i386.c (elf_i386_scan_relocs): Ignore protected
            visibility in shared libraries on Solaris.
            * elf64-x86-64.c (elf_x86_64_scan_relocs): Likewise.

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]