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 rtl-optimization/98287] [10/11 Regression] ICE: in expand_expr_real_2, at expr.c:10000 with -O2 -fno-tree-ccp -fno-tree-forwprop Date: Mon, 01 Feb 2021 12:39:34 +0000 [thread overview] Message-ID: <bug-98287-4-eiu1RyobHH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98287-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98287 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 50108 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50108&action=edit gcc11-pr98287.patch I'd be afraid it could be hundreds of patterns potentially affected by this. So I think it is much easier to handle that in the infrastructure. This patch attempts to do that when PROP_gimple_lvec property is set for cases for which expand_vector_operations_1 does something (except I've skipped the VEC_PERM_EXPR and VEC_COND_EXPR/COND_EXPR checks for now).
next prev parent reply other threads:[~2021-02-01 12:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-15 12:43 [Bug rtl-optimization/98287] New: " zsojka at seznam dot cz 2020-12-15 14:02 ` [Bug rtl-optimization/98287] " jakub at gcc dot gnu.org 2020-12-21 11:22 ` zsojka at seznam dot cz 2021-01-04 15:10 ` rguenth at gcc dot gnu.org 2021-02-01 12:39 ` jakub at gcc dot gnu.org [this message] 2021-02-03 8:10 ` cvs-commit at gcc dot gnu.org 2021-02-03 8:11 ` [Bug rtl-optimization/98287] [10 " jakub at gcc dot gnu.org 2021-03-19 23:28 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:05 ` 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-98287-4-eiu1RyobHH@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).