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/100885] [12 Regression] ICE: in extract_constrain_insn, at recog.c:2671: insn does not satisfy its constraints: {sse4_1_zero_extendv8qiv8hi2}
Date: Thu, 03 Jun 2021 03:33:48 +0000 [thread overview]
Message-ID: <bug-100885-4-PaQdqzbGKN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100885-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100885
--- Comment #1 from Hongtao.liu <crazylht at gmail dot com> ---
152(define_register_constraint "Yw"
153 "TARGET_AVX512BW && TARGET_AVX512VL ? ALL_SSE_REGS : TARGET_SSE ? SSE_REGS
: NO_REGS"
154 "@internal Any EVEX encodable SSE register (@code{%xmm0-%xmm31}) for
AVX512BW with TARGET_AVX512VL target, otherwise any \
SSE register.")
19076(define_insn "sse4_1_<code>v8qiv8hi2<mask_name>"
19077 [(set (match_operand:V8HI 0 "register_operand" "=Yr,*x,Yw")
19078 (any_extend:V8HI
19079 (vec_select:V8QI
19080 (match_operand:V16QI 1 "register_operand" "Yr,*x,Yw")
19081 (parallel [(const_int 0) (const_int 1)
19082 (const_int 2) (const_int 3)
19083 (const_int 4) (const_int 5)
19084 (const_int 6) (const_int 7)]))))]
19085 "TARGET_SSE4_1 && <mask_avx512bw_condition> &&
<mask_avx512vl_condition>"
19086 "%vpmov<extsuffix>bw\t{%1, %0<mask_operand2>|%0<mask_operand2>, %1}"
19087 [(set_attr "isa" "noavx,noavx,avx")
19088 (set_attr "type" "ssemov")
19089 (set_attr "prefix_extra" "1")
19090 (set_attr "prefix" "orig,orig,maybe_evex")
19091 (set_attr "mode" "TI")])
With avx512vl Yw should be matched, and w/o avx512bw, only SSE_REGS should be
matched, why xmm16 is allocated?
next prev parent reply other threads:[~2021-06-03 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 20:51 [Bug target/100885] New: " zsojka at seznam dot cz
2021-06-03 3:33 ` crazylht at gmail dot com [this message]
2021-06-03 3:49 ` [Bug target/100885] " crazylht at gmail dot com
2021-06-03 5:10 ` crazylht at gmail dot com
2021-06-03 7:14 ` crazylht at gmail dot com
2021-06-03 10:40 ` crazylht at gmail dot com
2021-06-07 3:28 ` cvs-commit at gcc dot gnu.org
2021-06-07 4:38 ` cvs-commit at gcc dot gnu.org
2021-06-07 4:41 ` crazylht at gmail dot com
2021-06-07 9:04 ` rguenth at gcc dot gnu.org
2021-06-07 14:49 ` cvs-commit at gcc dot gnu.org
2021-06-07 14:59 ` cvs-commit 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-100885-4-PaQdqzbGKN@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).