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/99767] [9/10/11 Regression] ICE in expand_direct_optab_fn, at internal-fn.c:3360 Date: Thu, 25 Mar 2021 15:22:38 +0000 [thread overview] Message-ID: <bug-99767-4-Oj1IYC6r1t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99767-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99767 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah, I don't see a problem on the omp simd cloning side, one could write such code by hand too. The thing is the DCE disabling, ifcvt adds .COND_DIV on the to be vectorized loop copy only, but in the end the loop is vectorized but .COND_DIV is not because it is dead and the vectorizer supposedly only considers statements that are actually used. So, either the vectorizer should do something for the dead statements in the loop (whatever, including failing the vectorization, or vectorizing them too, ...), or ifcvt shouldn't add those for the dead statements, or we need to lower those ifns back into scalar statements at the end of vectorization, or be able to expand them even when scalar.
next prev parent reply other threads:[~2021-03-25 15:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-25 11:19 [Bug target/99767] New: " asolokha at gmx dot com 2021-03-25 11:57 ` [Bug target/99767] " rguenth at gcc dot gnu.org 2021-03-25 11:57 ` rguenth at gcc dot gnu.org 2021-03-25 15:22 ` jakub at gcc dot gnu.org [this message] 2021-03-25 15:27 ` jakub at gcc dot gnu.org 2021-04-15 13:09 ` rguenth at gcc dot gnu.org 2021-04-15 14:58 ` jakub at gcc dot gnu.org 2021-04-15 15:32 ` jakub at gcc dot gnu.org 2021-04-16 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-16 9:58 ` [Bug target/99767] [9/10 " jakub at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:53 ` [Bug target/99767] [9 " jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 15:01 ` 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-99767-4-Oj1IYC6r1t@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).