public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105960] Crash in 32-bit mode
Date: Tue, 14 Jun 2022 08:30:57 +0000	[thread overview]
Message-ID: <bug-105960-4-qXW7scNu4D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105960-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|x86_64                      |i?86-*-*
   Last reconfirmed|                            |2022-06-14
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
                 CC|                            |hjl.tools at gmail dot com

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  Something is wrong with either ld.so or GCC.  We end up with

        .globl  exp_ref
        .type   exp_ref, @function
exp_ref:
.LFB1:
        .cfi_startproc
        pushl   %ebx
        .cfi_def_cfa_offset 8
        .cfi_offset 3, -8
        popl    %ebx
        .cfi_restore 3
        .cfi_def_cfa_offset 4
        jmp     expfull_ref@PLT

^^^ this crashes

        .type   expfull_ref, @gnu_indirect_function
        .set    expfull_ref,expfull_ref.resolver

        .type   expfull_ref.resolver, @function
expfull_ref.resolver:
.LFB4:
        .cfi_startproc
        pushl   %ebx

but expfull_ref isn't .globl!?


#define TARGET_CLONES  __attribute__((target_clones("default","fma")))
TARGET_CLONES
static inline double
expfull_ref(double x)
{
  return __builtin_pow(x, 0.1234);
}

double
exp_ref(double x)
{
  return expfull_ref(x);
}

  parent reply	other threads:[~2022-06-14  8:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 19:54 [Bug c/105960] New: " terra at gnome dot org
2022-06-13 20:00 ` [Bug target/105960] " pinskia at gcc dot gnu.org
2022-06-13 20:00 ` pinskia at gcc dot gnu.org
2022-06-13 20:06 ` terra at gnome dot org
2022-06-13 20:08 ` terra at gnome dot org
2022-06-14  8:30 ` rguenth at gcc dot gnu.org [this message]
2022-06-14  8:31 ` [Bug target/105960] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-06-14 14:18 ` hjl.tools at gmail dot com
2022-06-14 15:02 ` hjl.tools at gmail dot com
2022-06-14 17:22 ` wwcsmail at gmail dot com
2022-06-20 15:26 ` cvs-commit at gcc dot gnu.org
2022-06-21 17:45 ` cvs-commit at gcc dot gnu.org
2022-07-15  9:00 ` marxin at gcc dot gnu.org
2022-07-15 18:07 ` hjl.tools at gmail dot com

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-105960-4-qXW7scNu4D@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).