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 middle-end/104307] [11/12 Regression] '-fcompare-debug' failure (length) w/ -mavx512f -O2 Date: Mon, 31 Jan 2022 16:53:29 +0000 [thread overview] Message-ID: <bug-104307-4-0Zd5GYw47V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104307-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104307 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 52320 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52320&action=edit gcc12-pr104307.patch Untested fix. Just the first part of the hunk is needed for this bug, I'm actually not 100% sure about the rhs2/rhs3 case, but it feels it isn't right (it would e.g. try to expand_vector_condition the same stmt multiple times). I must say I don't understand the pushing of all uses into a vector, wouldn't it make more sense to push there just the VEC_COND_EXPRs with such lhs? Then we e.g. wouldn't need to do any expand_vector_condition calls if we have 1000 VEC_COND_EXPR uses and then a different use.
next prev parent reply other threads:[~2022-01-31 16:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 14:37 [Bug target/104307] New: " asolokha at gmx dot com 2022-01-31 14:38 ` [Bug target/104307] " asolokha at gmx dot com 2022-01-31 16:34 ` jakub at gcc dot gnu.org 2022-01-31 16:43 ` [Bug middle-end/104307] " jakub at gcc dot gnu.org 2022-01-31 16:53 ` jakub at gcc dot gnu.org [this message] 2022-02-01 15:06 ` [Bug tree-optimization/104307] " cvs-commit at gcc dot gnu.org 2022-02-01 15:10 ` [Bug tree-optimization/104307] [11 " jakub at gcc dot gnu.org 2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:08 ` 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-104307-4-0Zd5GYw47V@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).