public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhroma at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94167] New: pr71109.c -fcompare-debug failures on x86_64 and powerpc64le
Date: Fri, 13 Mar 2020 13:11:57 +0000 [thread overview]
Message-ID: <bug-94167-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94167
Bug ID: 94167
Summary: pr71109.c -fcompare-debug failures on x86_64 and
powerpc64le
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: zhroma at gcc dot gnu.org
Target Milestone: ---
Running
gcc -O2 -fcompare-debug gcc/testsuite/gcc.c-torture/compile/pr71109.c
fails with recent master on powerpc64le.
I also checked that same happens on x86 with recent 9.3.0 and old 5.5.0 ubuntu.
On master, first dump file with difference is fixup_cfg3
--
I've compared (on powerpc64le) usual regtest results and '-fcompare-debug'
results and there are like ~10 more failures, two of them already reported as
PR94166.
Certainly, there are actually a lot of cases when -fcompare-debug dumps
differs, but .o files have same code, so that can only be catched "manually"
(e.g. using RUNTESTFLAGS="--target_board=unix/-fcompare-debug" or bootstrapping
--with-build-config=bootstrap-debug-lean). And I'm not sure how much community
bothers about fixing issues like this one.
next reply other threads:[~2020-03-13 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 13:11 zhroma at gcc dot gnu.org [this message]
2020-03-13 14:16 ` [Bug debug/94167] [8/9/10 Regression] " jakub at gcc dot gnu.org
2020-03-13 14:37 ` jakub at gcc dot gnu.org
2020-03-13 15:35 ` jakub at gcc dot gnu.org
2020-03-16 8:05 ` cvs-commit at gcc dot gnu.org
2020-03-16 8:10 ` [Bug debug/94167] [8/9 " jakub at gcc dot gnu.org
2020-03-17 18:57 ` cvs-commit at gcc dot gnu.org
2020-03-17 19:14 ` [Bug debug/94167] [8 " jakub at gcc dot gnu.org
2020-09-17 14:25 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:19 ` 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-94167-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).