From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: "sunil.k.pandey" <skpandey@sc.intel.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
gcc-regression@gcc.gnu.org
Subject: Re: [r12-4397 Regression] FAIL: gcc.dg/guality/pr54200.c -Og -DPREVENT_OPTIMIZATION line 20 z == 3 on Linux/x86_64
Date: Fri, 15 Oct 2021 12:02:26 -0700 [thread overview]
Message-ID: <CAMe9rOqfBpRUrt0V-QZSh2b8LtCEmJ-bVXOAoSTRBW9HihE2vw@mail.gmail.com> (raw)
In-Reply-To: <6bec070e-55f1-5298-6b8c-7c39688f3f61@suse.cz>
On Fri, Oct 15, 2021 at 2:00 AM Martin Liška <mliska@suse.cz> wrote:
>
> On 10/14/21 21:16, sunil.k.pandey wrote:
> > FAIL: gcc.dg/guality/pr54200.c -Og -DPREVENT_OPTIMIZATION line 20 z == 3
>
> Hello.
>
> I've just verified the assembly is identical before and after the revision.
> So it must be a false positive.
>
> Cheers,
> Martin
I saw
Breakpoint 1, foo (z=3, x=<optimized out>, b=1) at
/export/gnu/import/git/gitlab/x86-gcc/gcc/testsuite/gcc.dg/guality/pr54200.c:20^M
20 return a; /* { dg-final { gdb-test . "z" "3" { xfail {
aarch64*-*-* && { no-opts "-O0" "-Og" } } } } } */^M
$1 = [uninitialized] 3^M
$2 = 3^M
A debugging session is active.^M
^M
Inferior 1 [process 4053185] will be killed.^M
^M
Quit anyway? (y or n) [answered Y; input not from terminal]^M
[uninitialized] 3 != 3
FAIL: gcc.dg/guality/pr54200.c -Og -DPREVENT_OPTIMIZATION line 20 z == 3
I don't know where [uninitialized] came from. I can't reproduce it
when I run gdb by hand.
--
H.J.
prev parent reply other threads:[~2021-10-15 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 19:16 sunil.k.pandey
2021-10-15 9:00 ` Martin Liška
2021-10-15 19:02 ` H.J. Lu [this message]
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=CAMe9rOqfBpRUrt0V-QZSh2b8LtCEmJ-bVXOAoSTRBW9HihE2vw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=skpandey@sc.intel.com \
/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).