public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/99230] [11 Regression] gcc.dg/pr83527.c excess errors: '-fcompare-debug' failure (length)
Date: Wed, 24 Feb 2021 16:59:16 +0000 [thread overview]
Message-ID: <bug-99230-4-NYSUmQrC0K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99230-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99230
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
On x86_64-linux I can reproduce the *.gimple dump discrepancies with
-O2 -fcompare-debug --param logical-op-non-short-circuit=0
diff -up pr83527.c.006t.gimple pr83527.gk.c.006t.gimple
--- pr83527.c.006t.gimple 2021-02-24 17:56:57.066963901 +0100
+++ pr83527.gk.c.006t.gimple 2021-02-24 17:56:57.536958750 +0100
@@ -3,23 +3,31 @@ void fn1 ()
int c;
short int d;
+ # DEBUG BEGIN_STMT
+ # DEBUG BEGIN_STMT
+ # DEBUG BEGIN_STMT
a.0_1 = a;
switch (a.0_1) <default: <D.1961>, case 32769: <D.1953>, case 32771:
<D.1954>, case 32772: <D.1955>, case 32782: <D.1956>, case 32800: <D.1952>>
<D.1952>:
+ # DEBUG BEGIN_STMT
fn2 ();
<D.1953>:
+ # DEBUG BEGIN_STMT
b = 0;
<D.1954>:
<D.1955>:
<D.1956>:
+ # DEBUG BEGIN_STMT
fn3 ();
<D.1961>:
- if (d != 0) goto <D.1962>; else goto <D.1963>;
- <D.1963>:
- if (c != 0) goto <D.1964>; else goto <D.1965>;
+ # DEBUG BEGIN_STMT
+ if (d != 0) goto <D.1962>; else goto <D.1964>;
<D.1964>:
- <D.1965>:
+ if (c != 0) goto <D.1962>; else goto <D.1963>;
<D.1962>:
+ # DEBUG BEGIN_STMT
+ # DEBUG BEGIN_STMT
+ <D.1963>:
}
which looks to me incorrect.
Without that param,
diff -up pr83527.c.006t.gimple pr83527.gk.c.006t.gimple
--- pr83527.c.006t.gimple 2021-02-24 17:58:39.484841634 +0100
+++ pr83527.gk.c.006t.gimple 2021-02-24 17:58:39.967836342 +0100
@@ -3,22 +3,31 @@ void fn1 ()
int c;
short int d;
+ # DEBUG BEGIN_STMT
+ # DEBUG BEGIN_STMT
+ # DEBUG BEGIN_STMT
a.0_1 = a;
switch (a.0_1) <default: <D.1961>, case 32769: <D.1953>, case 32771:
<D.1954>, case 32772: <D.1955>, case 32782: <D.1956>, case 32800: <D.1952>>
<D.1952>:
+ # DEBUG BEGIN_STMT
fn2 ();
<D.1953>:
+ # DEBUG BEGIN_STMT
b = 0;
<D.1954>:
<D.1955>:
<D.1956>:
+ # DEBUG BEGIN_STMT
fn3 ();
<D.1961>:
+ # DEBUG BEGIN_STMT
_2 = d != 0;
_3 = c != 0;
_4 = _2 | _3;
if (_4 != 0) goto <D.1962>; else goto <D.1963>;
<D.1962>:
+ # DEBUG BEGIN_STMT
+ # DEBUG BEGIN_STMT
<D.1963>:
}
looks good. But probably cris and x86_64 has different cswitch lowering later.
next prev parent reply other threads:[~2021-02-24 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 21:40 [Bug debug/99230] New: " hp at gcc dot gnu.org
2021-02-23 21:42 ` [Bug debug/99230] " hp at gcc dot gnu.org
2021-02-24 8:30 ` rguenth at gcc dot gnu.org
2021-02-24 16:59 ` jakub at gcc dot gnu.org [this message]
2021-02-26 12:59 ` rguenth at gcc dot gnu.org
2021-03-01 11:53 ` jakub at gcc dot gnu.org
2021-03-01 12:46 ` jakub at gcc dot gnu.org
2021-03-17 18:56 ` jakub at gcc dot gnu.org
2021-03-18 14:57 ` hp at gcc dot gnu.org
2021-03-20 16:02 ` cvs-commit at gcc dot gnu.org
2021-03-24 15:09 ` jakub 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-99230-4-NYSUmQrC0K@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).