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 target/95713] [10/11 Regression] ICE in emit_move_insn when converting int2 vector to short2 vector for -march=skylake-avx512 since r10-5031-g78307657cf9675bc
Date: Wed, 17 Jun 2020 06:54:53 +0000 [thread overview]
Message-ID: <bug-95713-4-MxRcO0Z5vn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95713-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95713
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|i?86-*-* |x86_64-*-* i?86-*-*
Target Milestone|--- |10.2
CC| |hjl.tools at gmail dot com,
| |kyukhin at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the expansion of
b_4 = VEC_PACK_TRUNC_EXPR <_2, _7>;
with two V1SI operands results in a DImode rtx (reg:DI 93) but RTL
expansion wants to see it in (reg:SI 84) (that is b). But the
simplistic code doing that doesn't work (obviously):
temp = force_operand (temp, target);
if (temp != target)
emit_move_insn (target, temp);
I guess the expansion of VEC_PACK_TRUNC_EXPR is "wrong". We do have
CODE_FOR_vec_pack_trunc_si but that maps to
(define_expand "vec_pack_trunc_<mode>"
[(set (match_operand:<DOUBLEMASKMODE> 0 "register_operand")
(ior:<DOUBLEMASKMODE>
(ashift:<DOUBLEMASKMODE>
(zero_extend:<DOUBLEMASKMODE>
(match_operand:SWI24 2 "register_operand"))
(match_dup 3))
(zero_extend:<DOUBLEMASKMODE>
(match_operand:SWI24 1 "register_operand"))))]
"TARGET_AVX512BW"
where expand_binop_directly does
1098 if (binoptab == vec_pack_trunc_optab
...
1106 /* The mode of the result is different then the mode of the
1107 arguments. */
1108 tmp_mode = insn_data[(int) icode].operand[0].mode;
and tmp_mode ends up as DImode. Shouldn't the pattern use HALFMASKMODE?
Are those patterns supposed to only trigger for VECTOR_BOOLEAN and not
"generic" vectors mapping to integer modes?
next prev parent reply other threads:[~2020-06-17 6:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 20:12 [Bug rtl-optimization/95713] New: [10/11 Regression] ICE in emit_move_insn when converting int2 vector to short2 vector for -march=skylake-avx512 -m32 kretz at kde dot org
2020-06-17 6:23 ` [Bug target/95713] [10/11 Regression] ICE in emit_move_insn when converting int2 vector to short2 vector for -march=skylake-avx512 since r10-5031-g78307657cf9675bc marxin at gcc dot gnu.org
2020-06-17 6:54 ` rguenth at gcc dot gnu.org [this message]
2020-06-17 6:59 ` rguenth at gcc dot gnu.org
2020-06-17 8:46 ` jakub at gcc dot gnu.org
2020-06-17 9:53 ` jakub at gcc dot gnu.org
2020-06-18 8:25 ` kretz at kde dot org
2020-06-18 10:13 ` cvs-commit at gcc dot gnu.org
2020-06-18 10:18 ` cvs-commit at gcc dot gnu.org
2020-06-29 9:56 ` 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-95713-4-MxRcO0Z5vn@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).