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/104180] New: [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O1 Date: Sat, 22 Jan 2022 08:31:36 +0000 [thread overview] Message-ID: <bug-104180-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104180 Bug ID: 104180 Summary: [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -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: --- g++ 12.0.0 20220109 snapshot (g:90045c5df5b3c8853e7740fb72a11aead1c489bb) fails -fcompare-debug check when compiling the following testcase, reduced from gcc/testsuite/gcc.dg/torture/pr89223.c, w/ -O1: int a[5]; void c () { unsigned int b; for (b = 3; ; b--) a[b] = ({ a[b + 1]; }); } % g++-12.0.0 -O1 -fcompare-debug -c lluhupiv.c g++-12.0.0: error: lluhupiv.c: '-fcompare-debug' failure (length) --- lluhupiv.c.gkd 2022-01-22 15:27:16.168639041 +0700 +++ lluhupiv.gk.c.gkd 2022-01-22 15:27:16.239634334 +0700 @@ -33,7 +33,7 @@ (nil)) (insn # 0 0 3 (set (mem:SI (plus:DI (mult:DI (reg:DI 2 cx [orig:87 b ] [87]) (const_int 4 [0x4])) - (reg/f:DI 5 di [86])) [ a[b_3]+0 S4 A32]) + (reg/f:DI 5 di [86])) [ MEM <int[5]> [(int *)&a][b_3]+0 S4 A32]) (reg:SI 4 si [orig:82 _2 ] [82])) "lluhupiv.c":9:10# {*movsi_internal} (expr_list:REG_DEAD (reg:SI 4 si [orig:82 _2 ] [82]) (expr_list:REG_DEAD (reg:DI 2 cx [orig:87 b ] [87])
next reply other threads:[~2022-01-22 8:31 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-22 8:31 asolokha at gmx dot com [this message] 2022-01-22 11:13 ` [Bug debug/104180] " jakub at gcc dot gnu.org 2022-01-22 12:06 ` [Bug c++/104180] " pinskia at gcc dot gnu.org 2022-01-22 12:07 ` pinskia at gcc dot gnu.org 2022-01-22 12:19 ` jakub at gcc dot gnu.org 2022-01-24 9:10 ` rguenth at gcc dot gnu.org 2022-01-24 9:30 ` asolokha at gmx dot com 2022-02-17 6:23 ` aoliva at gcc dot gnu.org 2022-06-28 10:47 ` [Bug c++/104180] [10/11/12/13 " jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug c++/104180] [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-104180-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: linkBe 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).