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/110227] [13/14 Regression] gcc generates invalid AVX-512 code
Date: Tue, 13 Jun 2023 03:06:59 +0000 [thread overview]
Message-ID: <bug-110227-4-DmNWIV1N5N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110227-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110227
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> Semi-Reduced testcase:
> ```
> #include <immintrin.h>
>
> void f()
> {
> __m256i mask = _mm256_set_epi32(0, 0, 0, 0, -1, -1, -1, -1);
> register __m256i reg asm("xmm16") = mask;
> asm(""::"v"(reg));
> }
> ```
>
> Most likely introduced by r13-2804-ga282f086ef26d9 .
(define_insn "mov<mode>_internal"
[(set (match_operand:VMOVE 0 "nonimmediate_operand"
- "=v,v ,v ,m")
+ "=v,v ,v,v ,m")
(match_operand:VMOVE 1 "nonimmediate_or_sse_const_operand"
- " C,<sseconstm1>,vm,v"))]
+ " C,<sseconstm1>,BH,vm,v"))]
We need to use "x" instead of "v".
next prev parent reply other threads:[~2023-06-13 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 14:47 [Bug target/110227] New: " joseph.weening at gmail dot com
2023-06-12 14:51 ` [Bug target/110227] " joseph.weening at gmail dot com
2023-06-12 15:43 ` [Bug target/110227] [13/14 Regression] " pinskia at gcc dot gnu.org
2023-06-13 3:06 ` crazylht at gmail dot com [this message]
2023-06-13 11:41 ` jakub at gcc dot gnu.org
2023-06-13 13:55 ` rguenth at gcc dot gnu.org
2023-06-14 8:19 ` cvs-commit at gcc dot gnu.org
2023-06-14 8:20 ` cvs-commit at gcc dot gnu.org
2023-06-14 8:21 ` crazylht at gmail dot com
2023-07-27 9:26 ` rguenth at gcc dot gnu.org
2023-11-30 10:54 ` liuhongt 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-110227-4-DmNWIV1N5N@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).