public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98694] [11 Regression] GCC produces incorrect code for loops with -O3 for skylake-avx512 and icelake-server
Date: Fri, 15 Jan 2021 17:33:05 +0000 [thread overview]
Message-ID: <bug-98694-4-wYt5JpLCL9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98694-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98694
--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #5)
> and rewritten pattern
> (define_insn "*vec_dupv4hi"
> [(set (match_operand:V4HI 0 "register_operand" "=y,xYw")
> (vec_duplicate:V4HI
> (truncate:HI
> (match_operand:SI 1 "register_operand" "0,xYw"))))]
> to
>
> (define_insn "*vec_dupv4hi"
> [(set (match_operand:V4HI 0 "register_operand" "=y,xYw")
> (vec_duplicate:V4HI
> (vecTselect:HI
> (match_operand:V4HI 1 "register_operand" "0,xYw")
> (parallel [(const_int 0)]))))]
>
> could avoid this issue.
Oh, not workable.
---
if (MAYBE_SSE_CLASS_P (regclass) || MAYBE_MMX_CLASS_P (regclass))
{
/* Vector registers do not support QI or HImode loads. If we don't
disallow a change to these modes, reload will assume it's ok to
drop the subreg from (subreg:SI (reg:HI 100) 0). This affects
the vec_dupv4hi pattern. */
if (GET_MODE_SIZE (from) < 4)
return
---
next prev parent reply other threads:[~2021-01-15 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 1:42 [Bug tree-optimization/98694] New: " vsevolod.livinskij at frtk dot ru
2021-01-15 8:11 ` [Bug tree-optimization/98694] " crazylht at gmail dot com
2021-01-15 9:43 ` [Bug target/98694] " marxin at gcc dot gnu.org
2021-01-15 10:03 ` [Bug target/98694] [11 Regression] " rguenth at gcc dot gnu.org
2021-01-15 16:52 ` crazylht at gmail dot com
2021-01-15 16:56 ` crazylht at gmail dot com
2021-01-15 17:22 ` crazylht at gmail dot com
2021-01-15 17:33 ` crazylht at gmail dot com [this message]
2021-01-18 9:41 ` crazylht at gmail dot com
2021-01-21 5:30 ` cvs-commit at gcc dot gnu.org
2021-01-21 5:33 ` crazylht at gmail dot com
2021-01-21 9:41 ` [Bug target/98694] " rguenth at gcc dot gnu.org
2021-01-21 11:12 ` crazylht at gmail dot com
2021-05-05 17:48 ` jakub at gcc dot gnu.org
2022-05-10 8:17 ` cvs-commit at gcc dot gnu.org
2022-10-28 23:30 ` pinskia 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-98694-4-wYt5JpLCL9@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).