public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95256] [11 Regression] ICE in convert_move, at expr.c:278 since r11-263-g7c355156aa20eaec
Date: Thu, 21 May 2020 18:38:39 +0000 [thread overview]
Message-ID: <bug-95256-4-ynZmomKH0k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95256-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95256
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |95125
CC| |crazylht at gmail dot com
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
This PR and PR95211 will be fixed by the for PR95125. Here, the offending
pattern should be renamed to something like
avx512dq_fix<fixunssuffix>_truncv2sfv2di2<mask_name>
and an expander should be added:
(define_expand "fix<fixunssuffix>_truncv2sfv2di2"
[(set (match_operand:V2DI 0 "register_operand")
(any_fix:V2DI
(match_operand:V2SF 1 "nonimmediate_operand")))]
"TARGET_AVX512DQ && TARGET_AVX512VL"
{
if (!MEM_P (operands[1]))
{
operands[1] = simplify_gen_subreg (V4SFmode, operands[1], V2SFmode, 0);
emit_insn (gen_avx512dq_fix<fixunssuffix>_truncv2sfv2di2 (operands[0],
operands[1]));
DONE;
}
})
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95125
[Bug 95125] Unoptimal code for vectorized conversions
next prev parent reply other threads:[~2020-05-21 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 10:26 [Bug target/95256] New: [11 Regression] ICE in convert_move, at expr.c:278 asolokha at gmx dot com
2020-05-21 13:16 ` [Bug target/95256] [11 Regression] ICE in convert_move, at expr.c:278 since r11-263-g7c355156aa20eaec marxin at gcc dot gnu.org
2020-05-21 18:26 ` ubizjak at gmail dot com
2020-05-21 18:38 ` ubizjak at gmail dot com [this message]
2020-05-26 3:41 ` cvs-commit at gcc dot gnu.org
2020-05-28 17:14 ` asolokha at gmx dot com
2020-05-29 8:31 ` crazylht at gmail dot com
2020-05-29 10:06 ` asolokha at gmx 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-95256-4-ynZmomKH0k@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).