public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100005] undefined reference to `_rdrand64_step'
Date: Fri, 09 Apr 2021 20:27:41 +0000	[thread overview]
Message-ID: <bug-100005-4-l5UxPUACXP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100005-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Andrew, this isn't really specific to a single target, rough numbers of
extern inline __gnu_inline__ intrinsics are:
     14 config/s390
    120 config/sparc
    603 config/rs6000
   4044 config/aarch64
   5659 config/i386
   7338 config/arm
and rough numbers of static inline intrinsics are:
     24 config/c6x
     26 config/rs6000
     69 config/arm
     99 config/mips
    112 config/aarch64

  parent reply	other threads:[~2021-04-09 20:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 17:10 [Bug c/100005] New: " thiago at kde dot org
2021-04-09 17:15 ` [Bug c/100005] " redi at gcc dot gnu.org
2021-04-09 17:20 ` segher at gcc dot gnu.org
2021-04-09 17:27 ` segher at gcc dot gnu.org
2021-04-09 18:05 ` thiago at kde dot org
2021-04-09 18:07 ` jakub at gcc dot gnu.org
2021-04-09 18:11 ` thiago at kde dot org
2021-04-09 18:13 ` jakub at gcc dot gnu.org
2021-04-09 18:23 ` jakub at gcc dot gnu.org
2021-04-09 18:59 ` hjl.tools at gmail dot com
2021-04-09 20:27 ` jakub at gcc dot gnu.org [this message]
2021-04-12  8:05 ` [Bug target/100005] " rguenth at gcc dot gnu.org
2021-04-12 15:19 ` thiago at kde dot org
2021-04-12 15:26 ` jakub at gcc dot gnu.org
2021-04-12 15:37 ` thiago at kde dot org
2021-04-12 15:42 ` jakub at gcc dot gnu.org
2021-09-29  8:36 ` pinskia at gcc dot gnu.org
2021-09-29  8:36 ` pinskia at gcc dot gnu.org
2023-06-14 19:11 ` pinskia 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-100005-4-l5UxPUACXP@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).