public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103624] ICE: in extract_insn, at recog.c:2769 (error: unrecognizable insn) Date: Sun, 12 Dec 2021 17:03:02 +0000 [thread overview] Message-ID: <bug-103624-4-kogSVIDSRO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103624-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103624 --- Comment #4 from Bill Schmidt <wschmidt at gcc dot gnu.org> --- __builtin_darn and __builtin_darn_raw are in the wrong stanza. Moving them to [power9-64] fixes it on my cross: diff --git a/gcc/config/rs6000/rs6000-builtin-new.def b/gcc/config/rs6000/rs6000-builtin-new.def index 30556e5c7f2..2becd96a36c 100644 --- a/gcc/config/rs6000/rs6000-builtin-new.def +++ b/gcc/config/rs6000/rs6000-builtin-new.def @@ -2799,15 +2799,9 @@ ; Miscellaneous P9 functions [power9] - signed long long __builtin_darn (); - DARN darn {} - signed int __builtin_darn_32 (); DARN_32 darn_32 {} - signed long long __builtin_darn_raw (); - DARN_RAW darn_raw {} - const signed int __builtin_dtstsfi_eq_dd (const int<6>, _Decimal64); TSTSFI_EQ_DD dfptstsfi_eq_dd {} @@ -2840,6 +2834,12 @@ void __builtin_altivec_stxvl (vsc, void *, long); STXVL stxvl {} + signed long long __builtin_darn (); + DARN darn {} + + signed long long __builtin_darn_raw (); + DARN_RAW darn_raw {} + const signed int __builtin_scalar_byte_in_set (signed int, signed long long); CMPEQB cmpeqb {}
next prev parent reply other threads:[~2021-12-12 17:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 10:52 [Bug target/103624] New: ICE: unrecognizable insn asolokha at gmx dot com 2021-12-10 9:08 ` [Bug target/103624] ICE: in extract_insn, at recog.c:2769 (error: unrecognizable insn) linkw at gcc dot gnu.org 2021-12-10 13:28 ` wschmidt at gcc dot gnu.org 2021-12-12 16:50 ` wschmidt at gcc dot gnu.org 2021-12-12 17:03 ` wschmidt at gcc dot gnu.org [this message] 2021-12-12 23:57 ` segher at gcc dot gnu.org 2021-12-13 13:38 ` wschmidt at gcc dot gnu.org 2021-12-13 16:18 ` wschmidt at gcc dot gnu.org 2021-12-14 0:55 ` segher at gcc dot gnu.org 2021-12-15 20:32 ` wschmidt at gcc dot gnu.org 2021-12-17 17:35 ` cvs-commit at gcc dot gnu.org 2021-12-17 17:35 ` cvs-commit at gcc dot gnu.org 2021-12-17 17:52 ` segher 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-103624-4-kogSVIDSRO@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).