public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dantipov at cloudlinux dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108495] [10/11/12/13 Regression] aarch64 ICE with __builtin_aarch64_rndr Date: Wed, 25 Jan 2023 08:40:28 +0000 [thread overview] Message-ID: <bug-108495-4-jF5NrIGsWm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108495 --- Comment #5 from Dmitry Antipov <dantipov at cloudlinux dot com> --- # cat t-rand.c #include <stdint.h> #include <arm_acle.h> int main(int argc, char *argv[]) { uint64_t v; __rndr(&v); return 0; } # gcc t-rand.c In file included from t-rand.c:2: /usr/lib/gcc/aarch64-redhat-linux/12/include/arm_acle.h: In function ‘main’: /usr/lib/gcc/aarch64-redhat-linux/12/include/arm_acle.h:313:1: error: inlining failed in call to ‘always_inline’ ‘__rndr’: target specific option mismatch 313 | __rndr (uint64_t *__res) | ^~~~~~ t-rand.c:6:3: note: called from here 6 | __rndr(&v); | ^~~~~~~~~~ So, what target-specific option is wrong if none of them was specified?
next prev parent reply other threads:[~2023-01-25 8:40 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-23 11:53 [Bug target/108495] New: " jakub at gcc dot gnu.org 2023-01-23 11:53 ` [Bug target/108495] " jakub at gcc dot gnu.org 2023-01-23 12:09 ` ktkachov at gcc dot gnu.org 2023-01-23 12:12 ` jakub at gcc dot gnu.org 2023-01-25 8:25 ` dantipov at cloudlinux dot com 2023-01-25 8:32 ` jakub at gcc dot gnu.org 2023-01-25 8:40 ` dantipov at cloudlinux dot com [this message] 2023-01-25 8:49 ` jakub at gcc dot gnu.org 2023-01-25 9:11 ` ktkachov at gcc dot gnu.org 2023-07-07 10:44 ` [Bug target/108495] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-21 5:23 ` pinskia at gcc dot gnu.org 2024-02-21 5:52 ` pinskia at gcc dot gnu.org 2024-02-21 6:04 ` pinskia at gcc dot gnu.org 2024-02-21 6:08 ` pinskia at gcc dot gnu.org 2024-02-21 6:10 ` pinskia at gcc dot gnu.org 2024-02-21 6:11 ` pinskia at gcc dot gnu.org 2024-02-21 17:19 ` 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-108495-4-jF5NrIGsWm@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: linkBe 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).