public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/105653] New: [10/11/12/13 Regression] '-fcompare-debug' failure w/ -O2
Date: Thu, 19 May 2022 06:18:20 +0000 [thread overview]
Message-ID: <bug-105653-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105653
Bug ID: 105653
Summary: [10/11/12/13 Regression] '-fcompare-debug' failure w/
-O2
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: compare-debug-failure
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: aarch64-linux-gnu
Created attachment 52992
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52992&action=edit
Testcase
g++ 13.0.0 20220515 snapshot (g:18547874ee205d830acb31f1e3c1c89fc7725c14) fails
-fcompare-debug check when compiling the attached testcase w/ -O2:
% aarch64-linux-gnu-g++-13.0.0 -O2 -fcompare-debug -c q9dyty2d.cpp
aarch64-linux-gnu-g++-13.0.0: error: q9dyty2d.cpp: '-fcompare-debug' failure
(length)
gkd diff:
--- q9dyty2d.cpp.gkd 2022-05-19 13:16:40.109118502 +0700
+++ q9dyty2d.gk.cpp.gkd 2022-05-19 13:16:40.167118178 +0700
@@ -729,9 +729,7 @@
(insn:TI # 0 0 (set (reg/f:DI 3 x3 [orig:113 MEM[(struct btVector3 * *)_31 +
8B] ] [113])
(mem/f:DI (plus:DI (reg:DI 2 x2 [orig:101 D.xxxx ] [101])
(const_int 8 [0x8])) [ MEM[(struct btVector3 * *)_31 + 8B]+0
S8 A64])) "q9dyty2d.cpp":39:17# {*movdi_aarch64}
- (expr_list:REG_EQUIV (mem/f:DI (plus:DI (reg:DI 2 x2 [orig:101 D.xxxx ]
[101])
- (const_int 8 [0x8])) [ MEM[(struct btVector3 * *)_31 + 8B]+0
S8 A64])
- (nil)))
+ (nil))
(jump_insn:TI # 0 0 (set (pc)
(if_then_else (ne (reg/f:DI 3 x3 [orig:113 MEM[(struct btVector3 *
*)_31 + 8B] ] [113])
(const_int 0 [0]))
@@ -899,9 +897,7 @@
(insn:TI # 0 0 (set (reg/f:DI 3 x3 [orig:112 MEM[(struct btVector3 * *)_30 +
8B] ] [112])
(mem/f:DI (plus:DI (reg:DI 2 x2 [orig:101 D.xxxx ] [101])
(const_int 8 [0x8])) [ MEM[(struct btVector3 * *)_30 + 8B]+0
S8 A64])) "q9dyty2d.cpp":39:17# {*movdi_aarch64}
- (expr_list:REG_EQUIV (mem/f:DI (plus:DI (reg:DI 2 x2 [orig:101 D.xxxx ]
[101])
- (const_int 8 [0x8])) [ MEM[(struct btVector3 * *)_30 + 8B]+0
S8 A64])
- (nil)))
+ (nil))
(jump_insn:TI # 0 0 (set (pc)
(if_then_else (ne (reg/f:DI 3 x3 [orig:112 MEM[(struct btVector3 *
*)_30 + 8B] ] [112])
(const_int 0 [0]))
next reply other threads:[~2022-05-19 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 6:18 asolokha at gmx dot com [this message]
2022-05-19 6:21 ` [Bug debug/105653] " rguenth at gcc dot gnu.org
2022-06-28 10:49 ` jakub at gcc dot gnu.org
2022-08-03 3:03 ` [Bug rtl-optimization/105653] " asolokha at gmx dot com
2022-10-27 0:42 ` pinskia at gcc dot gnu.org
2022-12-20 13:46 ` rguenth at gcc dot gnu.org
2023-07-07 10:43 ` [Bug rtl-optimization/105653] [11/12/13/14 " rguenth 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-105653-4@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).