From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: PING^1 [PATCH] i386: Disallow sibcall when calling ifunc functions with PIC register
Date: Mon, 20 Jun 2022 07:02:47 -0700 [thread overview]
Message-ID: <CAMe9rOrCE+VFfM0jV0qT0Ma43T4QOQEo+M3BUrFR2R6rFY8zYQ@mail.gmail.com> (raw)
In-Reply-To: <20220614192548.1929268-1-hjl.tools@gmail.com>
On Tue, Jun 14, 2022 at 12:25 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> Disallow siball when calling ifunc functions with PIC register so that
> PIC register can be restored.
>
> gcc/
>
> PR target/105960
> * config/i386/i386.cc (ix86_function_ok_for_sibcall): Return
> false if PIC register is used when calling ifunc functions.
>
> gcc/testsuite/
>
> PR target/105960
> * gcc.target/i386/pr105960.c: New test.
> ---
> gcc/config/i386/i386.cc | 9 +++++++++
> gcc/testsuite/gcc.target/i386/pr105960.c | 19 +++++++++++++++++++
> 2 files changed, 28 insertions(+)
> create mode 100644 gcc/testsuite/gcc.target/i386/pr105960.c
>
> diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc
> index 3d189e124e4..1ca7836e11e 100644
> --- a/gcc/config/i386/i386.cc
> +++ b/gcc/config/i386/i386.cc
> @@ -1015,6 +1015,15 @@ ix86_function_ok_for_sibcall (tree decl, tree exp)
> }
> }
>
> + if (decl && ix86_use_pseudo_pic_reg ())
> + {
> + /* When PIC register is used, it must be restored after ifunc
> + function returns. */
> + cgraph_node *node = cgraph_node::get (decl);
> + if (node && node->ifunc_resolver)
> + return false;
> + }
> +
> /* Otherwise okay. That also includes certain types of indirect calls. */
> return true;
> }
> diff --git a/gcc/testsuite/gcc.target/i386/pr105960.c b/gcc/testsuite/gcc.target/i386/pr105960.c
> new file mode 100644
> index 00000000000..db137a1642d
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/i386/pr105960.c
> @@ -0,0 +1,19 @@
> +/* { dg-do compile } */
> +/* { dg-require-ifunc "" } */
> +/* { dg-options "-O2 -fpic" } */
> +
> +__attribute__((target_clones("default","fma")))
> +static inline double
> +expfull_ref(double x)
> +{
> + return __builtin_pow(x, 0.1234);
> +}
> +
> +double
> +exp_ref(double x)
> +{
> + return expfull_ref(x);
> +}
> +
> +/* { dg-final { scan-assembler "jmp\[ \t\]*expfull_ref@PLT" { target { ! ia32 } } } } */
> +/* { dg-final { scan-assembler "call\[ \t\]*expfull_ref@PLT" { target ia32 } } } */
> --
> 2.36.1
>
PING.
--
H.J.
next prev parent reply other threads:[~2022-06-20 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 19:25 H.J. Lu
2022-06-20 14:02 ` H.J. Lu [this message]
2022-06-20 14:51 ` PING^1 " Uros Bizjak
2022-06-21 14:45 ` H.J. Lu
2022-06-21 14:53 ` Uros Bizjak
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=CAMe9rOrCE+VFfM0jV0qT0Ma43T4QOQEo+M3BUrFR2R6rFY8zYQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@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).