public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83782] [9/10/11/12 Regression] Inconsistent address for hidden ifunc in a shared library
Date: Fri, 03 Dec 2021 13:13:25 +0000	[thread overview]
Message-ID: <bug-83782-4-QRYBpSvQtT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83782-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83782

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

https://gcc.gnu.org/g:f7854b908977adce4ff669c4e0332ef868568b7c

commit r12-5771-gf7854b908977adce4ff669c4e0332ef868568b7c
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sat Jun 19 08:16:45 2021 -0700

    Add TARGET_IFUNC_REF_LOCAL_OK

    1. On some targets, like PowerPC, reference to ifunc function resolver
    must be non-local so that compiler will properly emit PLT call.  Add
    TARGET_IFUNC_REF_LOCAL_OK to allow binding indirect function resolver
    locally for targets which don't require special PLT call sequence.
    2. Add ix86_call_use_plt_p to call local ifunc function resolvers via
    PLT.

    gcc/

            PR target/51469
            PR target/83782
            * target.def (ifunc_ref_local_ok): Add a target hook.
            * varasm.c (default_binds_local_p_3): Force indirect function
            resolver non-local only if targetm.ifunc_ref_local_ok returns
            false.
            * config/i386/i386-expand.c (ix86_expand_call): Call
            ix86_call_use_plt_p to check if PLT should be used.
            * config/i386/i386-protos.h (ix86_call_use_plt_p): New.
            * config/i386/i386.c (output_pic_addr_const): Call
            ix86_call_use_plt_p to check if "@PLT" is needed.
            (ix86_call_use_plt_p): New.
            (TARGET_IFUNC_REF_LOCAL_OK): New.
            * doc/tm.texi.in: Add TARGET_IFUNC_REF_LOCAL_OK.
            * doc/tm.texi: Regenerated.

    gcc/testsuite/

            PR target/51469
            PR target/83782
            * gcc.target/i386/pr83782-1.c: New test.
            * gcc.target/i386/pr83782-2.c: Likewise.

  parent reply	other threads:[~2021-12-03 13:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-83782-4@http.gcc.gnu.org/bugzilla/>
2021-06-19 14:20 ` hjl.tools at gmail dot com
2021-07-06  6:44 ` rguenth at gcc dot gnu.org
2021-12-03 13:13 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-03 13:15 ` [Bug target/83782] [9/10/11 " hjl.tools at gmail dot com
2021-12-03 17:05 ` cvs-commit at gcc dot gnu.org
2022-05-27  9:38 ` [Bug target/83782] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:34 ` jakub at gcc dot gnu.org
2022-07-19  3:42 ` aoliva at gcc dot gnu.org
2022-07-19 15:26 ` hjl.tools at gmail dot com
2022-07-20 20:39 ` aoliva at gcc dot gnu.org
2022-07-20 21:44 ` hjl.tools at gmail dot com
2022-08-01 18:29 ` cvs-commit at gcc dot gnu.org
2023-07-07 10:32 ` [Bug target/83782] [11 " rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-83782-4-QRYBpSvQtT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).