public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/112494] ICE in ix86_cc_mode, at config/i386/i386.cc:16477
Date: Mon, 13 Nov 2023 07:57:12 +0000 [thread overview]
Message-ID: <bug-112494-4-bPawX2AH62@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112494-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112494
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I almost want to say this is a bug in the x86 back-end where it pushes the
flags onto the stack.
That is:
(insn 11 8 12 2 (set (mem:DI (pre_dec:DI (reg/f:DI 7 sp)) [0 S8 A8])
(reg:DI 17 flags))
"/opt/compiler-explorer/gcc-trunk-20231112/lib/gcc/x86_64-linux-gnu/14.0.0/include/ia32intrin.h":262:10
70 {*pushfldi2}
(expr_list:REG_DEAD (reg:DI 17 flags)
(nil)))
(insn 12 11 20 2 (set (reg:DI 102)
(mem:DI (post_inc:DI (reg/f:DI 7 sp)) [0 S8 A8]))
"/opt/compiler-explorer/gcc-trunk-20231112/lib/gcc/x86_64-linux-gnu/14.0.0/include/ia32intrin.h":262:10
66 {*popdi1}
(expr_list:REG_UNUSED (reg:DI 102)
(nil)))
(insn 20 12 21 2 (set (reg:CCZ 17 flags)
(compare:CCZ (reg/v:DI 98 [ flags1D.40416 ])
(const_int 0 [0]))) "/app/example.cpp":14:15 8 {*cmpdi_ccno_1}
(expr_list:REG_EQUAL (compare:CCZ (const_int 215 [0xd7])
(const_int 0 [0]))
(expr_list:REG_DEAD (reg/v:DI 98 [ flags1D.40416 ])
(nil))))
Maybe it should be represented as:
(set (mem:DI (pre_dec:DI (reg/f:DI 7 sp)) [0 S8 A8])
(unspec (reg:CC 17 flags) GET_EFLAGS))
Likewise for poping:
(set (reg:DI 17 flags)
(mem:DI (post_inc:DI (reg/f:DI 7 sp)) [0 S8 A8]))
(nil)
Should really be:
(set (reg:CC 17 flags)
(unspec:CC (mem:DI (post_inc:DI (reg/f:DI 7 sp)) [0 S8 A8]))
SET_EFLAGS))
next prev parent reply other threads:[~2023-11-13 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 14:25 [Bug c/112494] New: GCC: 14: internal compiler error: " 141242068 at smail dot nju.edu.cn
2023-11-12 20:57 ` [Bug rtl-optimization/112494] " ubizjak at gmail dot com
2023-11-12 21:12 ` [Bug rtl-optimization/112494] ICE " pinskia at gcc dot gnu.org
2023-11-13 7:57 ` pinskia at gcc dot gnu.org [this message]
2023-11-13 8:50 ` ubizjak at gmail dot com
2023-11-13 8:52 ` [Bug target/112494] " ubizjak at gmail dot com
2023-11-13 9:54 ` ubizjak at gmail dot com
2023-11-13 9:59 ` ubizjak at gmail dot com
2023-11-13 10:51 ` ubizjak at gmail dot com
2023-11-13 21:47 ` cvs-commit at gcc dot gnu.org
2023-11-28 15:57 ` cvs-commit at gcc dot gnu.org
2023-11-28 16:00 ` ubizjak at gmail 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-112494-4-bPawX2AH62@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).