public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/103756] [12 Regression] -fcompare-debug failure (length) with -O -fconserve-stack -frename-registers -fno-tree-ch -fira-algorithm=priority since r12-5978-ga888259a71fbbb7f
Date: Thu, 30 Dec 2021 21:26:45 +0000 [thread overview]
Message-ID: <bug-103756-4-i1QyzZcWfW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103756-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103756
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:6c684aa50d4eef28bb59ebb4664f362662845cd6
commit r12-6156-g6c684aa50d4eef28bb59ebb4664f362662845cd6
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Dec 30 22:25:34 2021 +0100
regrename: Fix -fcompare-debug issue in find_rename_reg [PR103756]
The r12-5978 change caused a -fcompare-debug issue, because without
-g a chain might start with a noop move, but with -g there could be
one or more DEBUG_INSNs in the chain before the noop move and so
regrename could make different decisions between -g and -g0.
Note, I must say I don't really understand the original change much,
if we want to make sure the noop moves are removed, couldn't regrename
during building of those du chains simply remove the noop moves instead?
2021-12-30 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/103756
* regrename.c (find_rename_reg): Test noop_move_p on the first
non-debug insn in the chain rather than on the first insn.
* g++.dg/opt/pr103756.C: New test.
next prev parent reply other threads:[~2021-12-30 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 8:11 [Bug debug/103756] New: [12 Regression] -fcompare-debug failure (length) with -O -fconserve-stack -frename-registers -fno-tree-ch -fira-algorithm=priority zsojka at seznam dot cz
2021-12-17 8:20 ` [Bug rtl-optimization/103756] " pinskia at gcc dot gnu.org
2021-12-17 8:47 ` [Bug rtl-optimization/103756] [12 Regression] -fcompare-debug failure (length) with -O -fconserve-stack -frename-registers -fno-tree-ch -fira-algorithm=priority since r12-5978-ga888259a71fbbb7f marxin at gcc dot gnu.org
2021-12-28 18:00 ` jakub at gcc dot gnu.org
2021-12-30 21:26 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-30 21:28 ` 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-103756-4-i1QyzZcWfW@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).