From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] sched1: Fix -fcompare-debug issue in schedule_region [PR105586]
Date: Wed, 31 Aug 2022 09:39:49 -0600 [thread overview]
Message-ID: <0312d474-d2de-6c68-5812-5b79f1176b0b@gmail.com> (raw)
In-Reply-To: <eb7f49a5-7e58-4a02-e4d1-f2d0cc0061e1@linux.vnet.ibm.com>
On 8/23/2022 5:49 AM, Surya Kumari Jangala via Gcc-patches wrote:
> sched1: Fix -fcompare-debug issue in schedule_region [PR105586]
>
> In schedule_region(), a basic block that does not contain any real insns
> is not scheduled and the dfa state at the entry of the bb is not copied
> to the fallthru basic block. However a DEBUG insn is treated as a real
> insn, and if a bb contains non-real insns and a DEBUG insn, it's dfa
> state is copied to the fallthru bb. This was resulting in
> -fcompare-debug failure as the incoming dfa state of the fallthru block
> is different with -g. We should always copy the dfa state of a bb to
> it's fallthru bb even if the bb does not contain real insns.
>
> 2022-08-22 Surya Kumari Jangala <jskumari@linux.ibm.com>
>
> gcc/
> PR rtl-optimization/105586
> * sched-rgn.cc (schedule_region): Always copy dfa state to
> fallthru block.
>
> gcc/testsuite/
> PR rtl-optimization/105586
> * gcc.target/powerpc/pr105586.c: New test.
Interesting. We may have stumbled over this bug internally a little
while ago -- not from a compare-debug standpoint, but from a "why isn't
the processor state copied to the fallthru block" point of view. I had
it on my to investigate list, but hadn't gotten around to it yet.
I think there were requests for ChangeLog updates and a function comment
for save_state_for_fallthru_edge. OK with those updates.
jeff
next prev parent reply other threads:[~2022-08-31 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 11:49 Surya Kumari Jangala
2022-08-23 12:55 ` Peter Bergner
2022-08-23 13:28 ` Segher Boessenkool
2022-08-24 8:10 ` Surya Kumari Jangala
2022-08-30 12:27 ` Richard Sandiford
2022-08-31 15:39 ` Jeff Law [this message]
2022-09-20 7:17 ` Surya Kumari Jangala
2022-09-21 7:33 ` Richard Biener
2022-11-08 16:36 ` Surya Kumari Jangala
2022-11-08 17:32 ` Richard Biener
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=0312d474-d2de-6c68-5812-5b79f1176b0b@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).