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/104407] New: [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -std=c++17 -O1
Date: Sun, 06 Feb 2022 07:32:56 +0000 [thread overview]
Message-ID: <bug-104407-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104407
Bug ID: 104407
Summary: [10/11/12 Regression] '-fcompare-debug' failure
(length) w/ -std=c++17 -O1
Product: gcc
Version: 12.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: x86_64-unknown-linux-gnu
gcc 12.0.1 20220130 snapshot (g:baf98320ac6cd56da0c0b460fb94e3b87a79220d) fails
-fcompare-debug check when compiling the following testcase, extracted from
gcc/testsuite/g++.dg/cpp1z/decomp13.C, w/ -O1:
struct A { int i; long j; int k : 2; char l; } a;
auto [ aa, bb, cc, dd ] = a;
namespace N
{
auto & [ m, n, o, ppp ] = a;
}
% x86_64-unknown-linux-gnu-g++-12.0.1 -O1 -fcompare-debug -c t3pwb1uu.C
x86_64-unknown-linux-gnu-g++-12.0.1: error: t3pwb1uu.C: '-fcompare-debug'
failure (length)
--- t3pwb1uu.C.gkd 2022-02-06 14:31:15.936434434 +0700
+++ t3pwb1uu.gk.C.gkd 2022-02-06 14:31:15.996430437 +0700
@@ -11,7 +11,7 @@
(note # 0 0 NOTE_INSN_FUNCTION_BEG)
(note # 0 0 NOTE_INSN_DELETED)
(insn # 0 0 2 (set (reg:TI 20 xmm0 [89])
- (mem/c:TI (symbol_ref:DI ("a") [flags 0x2] <var_decl # a>) [ a+0 S16
A128])) "t3pwb1uu.C":3:6# {*movti_internal}
+ (mem/c:TI (symbol_ref:DI ("a") [flags 0x2] <var_decl # a>) [ a+0 S16
A64])) "t3pwb1uu.C":3:6# {*movti_internal}
(nil))
(insn # 0 0 2 (set (mem/c:TI (symbol_ref:DI ("_ZDC2aa2bb2cc2ddE") [flags 0x2]
<var_decl # D.xxxx>) [ D.xxxx+0 S16 A128])
(reg:TI 20 xmm0 [89])) "t3pwb1uu.C":3:6# {*movti_internal}
@@ -19,9 +19,9 @@
(nil)))
(insn # 0 0 2 (set (reg:DI 0 ax [orig:87 a+16 ] [87])
(mem/c:DI (const:DI (plus:DI (symbol_ref:DI ("a") [flags 0x2]
<var_decl # a>)
- (const_int 16 [0x10]))) [ a+16 S8 A128]))
"t3pwb1uu.C":3:6# {*movdi_internal}
+ (const_int 16 [0x10]))) [ a+16 S8 A64])) "t3pwb1uu.C":3:6#
{*movdi_internal}
(expr_list:REG_EQUIV (mem/c:DI (const:DI (plus:DI (symbol_ref:DI ("a")
[flags 0x2] <var_decl # a>)
- (const_int 16 [0x10]))) [ a+16 S8 A128])
+ (const_int 16 [0x10]))) [ a+16 S8 A64])
(nil)))
(insn # 0 0 2 (set (mem/c:DI (const:DI (plus:DI (symbol_ref:DI
("_ZDC2aa2bb2cc2ddE") [flags 0x2] <var_decl # D.xxxx>)
(const_int 16 [0x10]))) [ D.xxxx+16 S8 A128])
next reply other threads:[~2022-02-06 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 7:32 asolokha at gmx dot com [this message]
2022-02-06 8:51 ` [Bug debug/104407] " pinskia at gcc dot gnu.org
2022-02-06 8:52 ` [Bug target/104407] " pinskia at gcc dot gnu.org
2022-02-07 9:05 ` jakub at gcc dot gnu.org
2022-02-07 9:17 ` jakub at gcc dot gnu.org
2022-02-07 9:19 ` jakub at gcc dot gnu.org
2022-02-07 9:23 ` jakub at gcc dot gnu.org
2022-02-07 9:31 ` rguenth at gcc dot gnu.org
2022-02-07 9:38 ` jakub at gcc dot gnu.org
2022-02-07 9:42 ` jakub at gcc dot gnu.org
2022-02-07 9:42 ` rguenth at gcc dot gnu.org
2022-02-07 9:44 ` rguenth at gcc dot gnu.org
2022-02-07 9:50 ` [Bug debug/104407] " jakub at gcc dot gnu.org
2022-02-07 10:50 ` rguenth at gcc dot gnu.org
2022-02-07 11:10 ` jakub at gcc dot gnu.org
2022-02-07 11:22 ` rguenther at suse dot de
2022-02-07 11:35 ` jakub at gcc dot gnu.org
2022-02-09 14:19 ` cvs-commit at gcc dot gnu.org
2022-02-09 14:19 ` [Bug debug/104407] [10/11 " jakub at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug debug/104407] [11 " 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-104407-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).