public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103625] ICE: in extract_insn, at recog.c:2769 (error: unrecognizable insn) Date: Fri, 10 Dec 2021 09:48:30 +0000 [thread overview] Message-ID: <bug-103625-4-uCLJGqxCqy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103625-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103625 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linkw at gcc dot gnu.org, | |wschmidt at gcc dot gnu.org --- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> --- Confirmed, started to fail from r12-5752. The __builtin_vec_vcmpeq_p for doubleword overload requires power8-vector. Its current stanza is vsx, but should be power8-vector. The related bifs are: const vsll __builtin_altivec_vcmpequd (vull, vull); const int __builtin_altivec_vcmpequd_p (int, vsll, vsll); const vsll __builtin_altivec_vcmpgtsd (vsll, vsll); const int __builtin_altivec_vcmpgtsd_p (int, vsll, vsll); const vsll __builtin_altivec_vcmpgtud (vull, vull); const int __builtin_altivec_vcmpgtud_p (int, vsll, vsll);
next prev parent reply other threads:[~2021-12-10 9:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 11:03 [Bug target/103625] New: " asolokha at gmx dot com 2021-12-10 9:48 ` linkw at gcc dot gnu.org [this message] 2021-12-10 13:28 ` [Bug target/103625] " wschmidt at gcc dot gnu.org 2021-12-10 13:29 ` wschmidt at gcc dot gnu.org 2021-12-12 16:55 ` wschmidt at gcc dot gnu.org 2021-12-12 16:55 ` wschmidt at gcc dot gnu.org 2021-12-13 2:23 ` linkw at gcc dot gnu.org 2021-12-13 13:27 ` wschmidt at gcc dot gnu.org 2021-12-13 13:28 ` wschmidt at gcc dot gnu.org 2021-12-13 16:19 ` wschmidt at gcc dot gnu.org 2021-12-14 17:20 ` cvs-commit at gcc dot gnu.org 2021-12-14 17:27 ` wschmidt 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-103625-4-uCLJGqxCqy@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).