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/106736] [13 Regression] ICE in gen_movxo, at config/rs6000/mma.md:333 Date: Thu, 25 Aug 2022 09:21:27 +0000 [thread overview] Message-ID: <bug-106736-4-yZkbuewywK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106736-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106736 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-08-25 CC| |bergner at gcc dot gnu.org, | |segher at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> --- Confirmed, this got exposed by r13-2062. The commit expects movxo and movoo optab are only used with MMA support (or change with vector pair support on Power10 later) and for related bif expansion erroring. I wonder if we want to support types __vector_quad and __vector_pair without MMA support (or supposed to be fixed with Power10 later). If no, we need to guard register_builtin_type under TARGET_MMA (TARGET_POWER10 later) for those types. If yes, we may need to revisit its supports.
next prev parent reply other threads:[~2022-08-25 9:21 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-25 5:55 [Bug target/106736] New: " asolokha at gmx dot com 2022-08-25 5:57 ` [Bug target/106736] " asolokha at gmx dot com 2022-08-25 8:31 ` rguenth at gcc dot gnu.org 2022-08-25 9:21 ` linkw at gcc dot gnu.org [this message] 2022-08-25 12:01 ` bergner at gcc dot gnu.org 2022-08-26 11:33 ` linkw at gcc dot gnu.org 2022-08-26 18:51 ` bergner at gcc dot gnu.org 2022-08-26 19:06 ` bergner at gcc dot gnu.org 2022-08-27 13:43 ` linkw at gcc dot gnu.org 2022-08-31 2:42 ` linkw at gcc dot gnu.org 2022-08-31 18:46 ` segher at gcc dot gnu.org 2022-08-31 19:34 ` bergner at gcc dot gnu.org 2022-08-31 21:00 ` segher at gcc dot gnu.org 2022-09-07 6:51 ` linkw at gcc dot gnu.org 2022-10-19 7:08 ` rguenth at gcc dot gnu.org 2022-12-21 3:07 ` cvs-commit at gcc dot gnu.org 2022-12-27 19:33 ` asolokha at gmx dot com 2023-01-03 2:01 ` linkw at gcc dot gnu.org 2023-01-03 6:56 ` asolokha at gmx dot com 2023-01-03 7:08 ` linkw at gcc dot gnu.org 2023-01-05 5:30 ` cvs-commit at gcc dot gnu.org 2023-01-05 5:32 ` cvs-commit at gcc dot gnu.org 2023-01-05 5:33 ` cvs-commit at gcc dot gnu.org 2023-01-05 5:36 ` linkw 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-106736-4-yZkbuewywK@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).