public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108599] [12/13 Regression] Incorrect code generation newer intel architectures
Date: Mon, 30 Jan 2023 14:10:50 +0000 [thread overview]
Message-ID: <bug-108599-4-tX0GqBxlNn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108599-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
cse2 still has correct:
(insn 28 27 29 2 (set (reg:V4DI 86)
(mem/u/c:V4DI (symbol_ref/u:DI ("*.LC2") [flags 0x2]) [0 S32 A256]))
"pr108599.C":6:49 1811 {movv4di_internal}
(expr_list:REG_EQUAL (const_vector:V4DI [
(const_int 16 [0x10]) repeated x2
(const_int 0 [0]) repeated x2
])
(nil)))
(insn 29 28 30 2 (set (mem/c:V4DI (plus:DI (reg/f:DI 19 frame)
(const_int -32 [0xffffffffffffffe0])) [0 MEM <vector(4) long
unsigned int> [(void *)&D.3338]+0 S32 A256])
(reg:V4DI 86)) "pr108599.C":6:49 1811 {movv4di_internal}
(expr_list:REG_DEAD (reg:V4DI 86)
(nil)))
...
(insn 35 33 36 2 (set (reg:OI 88 [ D.3338 ])
(mem/c:OI (plus:DI (reg/f:DI 19 frame)
(const_int -32 [0xffffffffffffffe0])) [2 D.3338+0 S32 A256]))
"pr108599.C":20:7 discrim 3 80 {*movoi_internal_avx}
(nil))
(insn 36 35 37 2 (set (mem:OI (reg/f:DI 7 sp) [0 S32 A64])
(reg:OI 88 [ D.3338 ])) "pr108599.C":20:7 discrim 3 80
{*movoi_internal_avx}
(expr_list:REG_DEAD (reg:OI 88 [ D.3338 ])
(nil)))
But dse1 turns it into incorrect:
(insn 28 27 53 2 (set (reg:V4DI 86)
(mem/u/c:V4DI (symbol_ref/u:DI ("*.LC2") [flags 0x2]) [0 S32 A256]))
"pr108599.C":6:49 1811 {movv4di_internal}
(expr_list:REG_EQUAL (const_vector:V4DI [
(const_int 16 [0x10]) repeated x2
(const_int 0 [0]) repeated x2
])
(nil)))
(insn 53 28 52 2 (set (reg:DI 94)
(const_int 16 [0x10])) "pr108599.C":6:49 82 {*movdi_internal}
(nil))
(insn 52 53 54 2 (set (reg:V4DI 93)
(vec_duplicate:V4DI (reg:DI 94))) "pr108599.C":6:49 8004 {vec_dupv4di}
(expr_list:REG_DEAD (reg:DI 94)
(nil)))
(insn 54 52 30 2 (set (reg:OI 92)
(subreg:OI (reg:V4DI 93) 0)) "pr108599.C":6:49 80 {*movoi_internal_avx}
(expr_list:REG_DEAD (reg:V4DI 93)
(expr_list:REG_EQUAL (const_wide_int 0x100000000000000010)
(nil))))
...
(insn 35 33 36 2 (set (reg:OI 88 [ D.3338 ])
(reg:OI 92)) "pr108599.C":20:7 discrim 3 80 {*movoi_internal_avx}
(expr_list:REG_DEAD (reg:OI 92)
(nil)))
next prev parent reply other threads:[~2023-01-30 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 13:18 [Bug c++/108599] New: Incorrect code generation newer intel architectures for gcc 12 and 13 balder at yahooinc dot com
2023-01-30 13:20 ` [Bug c++/108599] " balder at yahooinc dot com
2023-01-30 13:32 ` [Bug target/108599] " balder at yahooinc dot com
2023-01-30 13:49 ` [Bug target/108599] [12/13 Regression] Incorrect code generation newer intel architectures jakub at gcc dot gnu.org
2023-01-30 14:00 ` jakub at gcc dot gnu.org
2023-01-30 14:10 ` jakub at gcc dot gnu.org [this message]
2023-01-30 14:31 ` jakub at gcc dot gnu.org
2023-01-30 15:17 ` rguenth at gcc dot gnu.org
2023-01-30 15:19 ` jakub at gcc dot gnu.org
2023-01-31 9:12 ` cvs-commit at gcc dot gnu.org
2023-01-31 9:14 ` [Bug target/108599] [12 " jakub at gcc dot gnu.org
2023-02-09 11:54 ` balder at yahooinc dot com
2023-02-09 12:02 ` jakub at gcc dot gnu.org
2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org
2023-02-10 18:01 ` 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-108599-4-tX0GqBxlNn@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).