public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102080] [12 Regression] avx512vl related ICE, on firefox-92 gcc ICEs: in expand_insn, at optabs.c:7946 by r12-2679
Date: Fri, 27 Aug 2021 02:19:14 +0000 [thread overview]
Message-ID: <bug-102080-4-kJrAgkoo5p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102080-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
Keywords| |ice-on-valid-code
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Hongtao.liu from comment #4)
> diff --git a/test.c.032t.ccp1 b/test.c.033t.forwprop1
> index 5b18739..c6f0587 100644
> --- a/test.c.032t.ccp1
> +++ b/test.c.033t.forwprop1
> @@ -31,11 +31,12 @@ void EncodedFromDisplay ()
> __m256 __trans_tmp_11;
> vector(8) float _mm256_mul_ps___A.2_1;
> vector(8) float _mm256_mul_ps___B.3_2;
> + vector(8) <signed-boolean:32> _5;
> vector(8) float _mm256_blendv_ps___M.0_6;
> vector(8) float _mm256_blendv_ps___Y.1_7;
> vector(8) int _8;
> vector(8) <signed-boolean:32> _9;
> - vector(8) float _10;
> + vector(8) float _12;
>
> <bb 2> :
> _mm256_mul_ps___A.2_1 = _mm256_mul_ps___A;
> @@ -45,8 +46,9 @@ void EncodedFromDisplay ()
> _mm256_blendv_ps___Y.1_7 = _mm256_blendv_ps___Y;
> _8 = VIEW_CONVERT_EXPR<vector(8) int>(_mm256_blendv_ps___M.0_6);
> _9 = _8 < { 0, 0, 0, 0, 0, 0, 0, 0 };
> - _10 = VEC_COND_EXPR <_9, _mm256_blendv_ps___Y.1_7, __trans_tmp_11_4>;
> - IfThenElse___trans_tmp_9 = _10;
> + _5 = _8 >= { 0, 0, 0, 0, 0, 0, 0, 0 };
> + _12 = .COND_MUL (_5, _mm256_mul_ps___A.2_1, _mm256_mul_ps___B.3_2,
> _mm256_blendv_ps___Y.1_7);
> + IfThenElse___trans_tmp_9 = _12;
> return;
>
> fwprop1 should check if the type of _5 satisfies the predicate of cond_mul.
Actually this seems backwards ... what match pattern is doing this?
next prev parent reply other threads:[~2021-08-27 2:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 14:42 [Bug target/102080] New: [12 Regression] avx512vl related ICE, on firefox-92 gcc ICEs: in expand_insn, at optabs.c:7946 slyfox at gcc dot gnu.org
2021-08-26 14:46 ` [Bug target/102080] " slyfox at gcc dot gnu.org
2021-08-26 16:10 ` [Bug target/102080] [12 Regression] avx512vl related ICE, on firefox-92 gcc ICEs: in expand_insn, at optabs.c:7946 by r12-2679 hjl.tools at gmail dot com
2021-08-27 0:38 ` crazylht at gmail dot com
2021-08-27 2:16 ` crazylht at gmail dot com
2021-08-27 2:19 ` pinskia at gcc dot gnu.org [this message]
2021-08-27 2:23 ` pinskia at gcc dot gnu.org
2021-08-27 2:32 ` pinskia at gcc dot gnu.org
2021-08-27 2:33 ` pinskia at gcc dot gnu.org
2021-08-27 2:42 ` crazylht at gmail dot com
2021-08-27 2:52 ` [Bug middle-end/102080] " pinskia at gcc dot gnu.org
2021-08-27 5:17 ` crazylht at gmail dot com
2021-08-27 7:02 ` rguenth at gcc dot gnu.org
2021-08-27 8:29 ` marxin at gcc dot gnu.org
2021-08-27 8:30 ` marxin at gcc dot gnu.org
2021-09-16 8:35 ` cvs-commit at gcc dot gnu.org
2021-12-17 16:01 ` jakub at gcc dot gnu.org
2021-12-17 16:07 ` hjl.tools at gmail dot com
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-102080-4-kJrAgkoo5p@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: link
Be 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).