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/104459] New: [9/10/11/12 Regression] '-fcompare-debug' failure w/ -O2 -funswitch-loops -fno-tree-dce
Date: Wed, 09 Feb 2022 11:43:40 +0000 [thread overview]
Message-ID: <bug-104459-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104459
Bug ID: 104459
Summary: [9/10/11/12 Regression] '-fcompare-debug' failure w/
-O2 -funswitch-loops -fno-tree-dce
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: ---
gcc 12.0.1 20220206 snapshot (g:8eb329e963593342855b6072e5692659107337b7) fails
-fcompare-debug check when compiling the following testcase w/ -O2
-funswitch-loops -fno-tree-dce:
void
foo (int x, int y)
{
unsigned int a;
for (;;)
{
short int *p = (short int *) &x;
unsigned int q = 0;
a /= 2;
if (a)
{
q -= y;
while (q)
{
}
}
if (x)
{
for (q = 0; q != 1; q += 2)
{
unsigned int n;
n = *p ? 0 : q;
y += n < 1;
n = a || *p;
if (n % x == 0)
y /= x;
}
}
}
}
% gcc-12.0.1 -O2 -fcompare-debug -funswitch-loops -fno-tree-dce -c rfygrmu3.c
gcc-12.0.1: error: rfygrmu3.c: '-fcompare-debug' failure
--- rfygrmu3.c.gkd 2022-02-09 18:38:41.086339468 +0700
+++ rfygrmu3.gk.c.gkd 2022-02-09 18:38:41.117339440 +0700
@@ -32,7 +32,7 @@
(pc))) "rfygrmu3.c":20:10# {*jcc}
(expr_list:REG_DEAD (reg:CCZ 17 flags)
(int_list:REG_BR_PROB 118111604 (nil)))
- -> 18)
+ -> 19)
(code_label # 0 0 4 4 (nil) [1 uses])
(note # 0 0 [bb 4] NOTE_INSN_BASIC_BLOCK)
(insn:TI # 0 0 4 (set (reg/v:SI 36 r8 [orig:89 a ] [89])
@@ -79,7 +79,7 @@
(nil)
-> 3)
(barrier # 0 0)
-(code_label # 0 0 7 18 (nil) [1 uses])
+(code_label # 0 0 7 19 (nil) [1 uses])
(note # 0 0 [bb 7] NOTE_INSN_BASIC_BLOCK)
(insn:TI # 0 0 7 (set (reg:CCZ 17 flags)
(compare:CCZ (reg:HI 5 di [orig:94 x ] [94])
next reply other threads:[~2022-02-09 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 11:43 asolokha at gmx dot com [this message]
2022-02-09 12:03 ` [Bug rtl-optimization/104459] " rguenth at gcc dot gnu.org
2022-02-09 18:56 ` jakub at gcc dot gnu.org
2022-02-09 19:07 ` jakub at gcc dot gnu.org
2022-02-09 19:13 ` jakub at gcc dot gnu.org
2022-02-11 10:24 ` cvs-commit at gcc dot gnu.org
2022-02-11 11:00 ` [Bug rtl-optimization/104459] [9/10/11 " jakub at gcc dot gnu.org
2022-05-27 9:47 ` [Bug rtl-optimization/104459] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug rtl-optimization/104459] [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-104459-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).