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/106342] [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791 since r12-4240-g2b8453c401b699 Date: Wed, 10 Aug 2022 10:36:08 +0000 [thread overview] Message-ID: <bug-106342-4-UrLx6nO270@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106342-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106342 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- commit r13-1955-g2f17f489de47d46626ed85804c3b810547ef550e Author: Ilya Leoshkevich <iii@linux.ibm.com> Date: Fri Jul 29 16:14:10 2022 +0200 PR106342 - IBM zSystems: Provide vsel for all vector modes dg.exp=pr104612.c fails with an ICE on s390x, because copysignv2sf3 produces an insn that vsel<mode> is supposed to recognize, but can't, because it's not defined for V2SF. Fix by defining it for all vector modes supported by copysign<mode>3. gcc/ChangeLog: * config/s390/vector.md (V_HW_FT): New iterator. * config/s390/vx-builtins.md (vsel<mode>): Use V_HW_FT instead of V_HW. Unfortunately the commit didn't contain the PR number in the format hooks want. Are you going to backport this to 12.2 (RC this Friday)?
next prev parent reply other threads:[~2022-08-10 10:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-18 15:32 [Bug target/106342] New: [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791 mpolacek at gcc dot gnu.org 2022-07-18 15:33 ` [Bug target/106342] " mpolacek at gcc dot gnu.org 2022-07-18 15:35 ` mpolacek at gcc dot gnu.org 2022-07-19 6:40 ` rguenth at gcc dot gnu.org 2022-07-19 10:34 ` marxin at gcc dot gnu.org 2022-07-19 18:09 ` mpolacek at gcc dot gnu.org 2022-07-20 8:13 ` [Bug target/106342] [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791 since r12-4240-g2b8453c401b699 marxin at gcc dot gnu.org 2022-07-28 17:08 ` jakub at gcc dot gnu.org 2022-07-28 22:29 ` iii at linux dot ibm.com 2022-07-29 7:31 ` jakub at gcc dot gnu.org 2022-08-10 10:36 ` jakub at gcc dot gnu.org [this message] 2023-04-19 14:32 ` [Bug target/106342] [12/13/14 " iii at linux dot ibm.com 2023-05-08 12:25 ` rguenth at gcc dot gnu.org 2024-03-15 1:15 ` law 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-106342-4-UrLx6nO270@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).