public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103800] [12 Regression] ICE in vectorizable_phi, at tree-vect-loop.c:7861 with -O3 since r12-5626-g0194d92c35ca8b3a Date: Tue, 04 Jan 2022 14:46:56 +0000 [thread overview] Message-ID: <bug-103800-4-1AnqJ7pFbK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103800-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103800 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- So in this case we have an SLP tree for a merge PHI with scalar bools where we do t.c:10:12: note: using boolean precision 32 for iftmp.1_168 = pretmp_175 != 0; t.c:10:12: note: using boolean precision 16 for _177 = _176 != 0; t.c:10:12: note: using boolean precision 16 for iftmp.1_173 = PHI <iftmp.1_168(6), _177(7)> but pattern detection doesn't have any code to insert compensation on PHI edges. We now detect the mismatch but I fell foul of thinking it can only happen for non-bool vs. bool context ...
next prev parent reply other threads:[~2022-01-04 14:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-22 8:14 [Bug tree-optimization/103800] New: ICE in vectorizable_phi, at tree-vect-loop.c:7861 with -O3 -march=skylake-avx512 vsevolod.livinskij at frtk dot ru 2021-12-22 8:18 ` [Bug tree-optimization/103800] [12 Regression] ICE in vectorizable_phi, at tree-vect-loop.c:7861 with -O3 pinskia at gcc dot gnu.org 2021-12-22 9:00 ` [Bug tree-optimization/103800] [12 Regression] ICE in vectorizable_phi, at tree-vect-loop.c:7861 with -O3 since r12-5626-g0194d92c35ca8b3a marxin at gcc dot gnu.org 2021-12-22 9:00 ` marxin at gcc dot gnu.org 2022-01-03 13:27 ` rguenth at gcc dot gnu.org 2022-01-04 14:46 ` rguenth at gcc dot gnu.org [this message] 2022-01-04 15:52 ` cvs-commit at gcc dot gnu.org 2022-01-04 15:52 ` rguenth 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-103800-4-1AnqJ7pFbK@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).