public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104675] [9/10/11 Regression] ICE: in expand_expr_real_2, at expr.cc:9773 at -O with __real__ + __imag__ extraction Date: Tue, 29 Mar 2022 05:53:22 +0000 [thread overview] Message-ID: <bug-104675-4-BfyU0d4sdG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104675-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104675 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:1305c28bc0665504643ff364595b7d6bb222745d commit r11-9719-g1305c28bc0665504643ff364595b7d6bb222745d Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Feb 25 10:55:17 2022 +0100 match.pd: Don't create BIT_NOT_EXPRs for COMPLEX_TYPE [PR104675] We don't support BIT_{AND,IOR,XOR,NOT}_EXPR on complex types, &/|/^ are just rejected for them, and ~ is parsed as CONJ_EXPR. So, we should avoid simplifications which turn valid complex type expressions into something that will ICE during expansion. 2022-02-25 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/104675 * match.pd (-A - 1 -> ~A, -1 - A -> ~A): Don't simplify for COMPLEX_TYPE. * gcc.dg/pr104675-1.c: New test. * gcc.dg/pr104675-2.c: New test. (cherry picked from commit 758671b88b78d7629376b118ec6ca6bcfbabbd36)
next prev parent reply other threads:[~2022-03-29 5:53 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-24 10:24 [Bug rtl-optimization/104675] New: [9/10/11/12 " zsojka at seznam dot cz 2022-02-24 10:29 ` [Bug rtl-optimization/104675] " jakub at gcc dot gnu.org 2022-02-24 10:32 ` pinskia at gcc dot gnu.org 2022-02-24 10:52 ` jakub at gcc dot gnu.org 2022-02-24 11:00 ` [Bug tree-optimization/104675] " pinskia at gcc dot gnu.org 2022-02-24 11:13 ` jakub at gcc dot gnu.org 2022-02-24 14:28 ` glisse at gcc dot gnu.org 2022-02-25 9:56 ` cvs-commit at gcc dot gnu.org 2022-02-25 10:53 ` jakub at gcc dot gnu.org 2022-02-25 20:25 ` cvs-commit at gcc dot gnu.org 2022-02-25 20:27 ` [Bug tree-optimization/104675] [9/10/11 " jakub at gcc dot gnu.org 2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org 2022-03-30 8:15 ` [Bug tree-optimization/104675] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-104675-4-BfyU0d4sdG@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).