From: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [PATCH] sched1: Fix -fcompare-debug issue in schedule_region [PR105586]
Date: Tue, 8 Nov 2022 22:06:55 +0530 [thread overview]
Message-ID: <be914ec4-3bc7-823d-7317-f07a6d3b3eee@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFiYyc3MKt0+1tmG34cSujWFSYbTZnneWY2Uwo0UG30fmKJcZw@mail.gmail.com>
Hi Richard,
On 21/09/22 1:03 pm, Richard Biener wrote:
> On Tue, Sep 20, 2022 at 9:18 AM Surya Kumari Jangala via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>>
>> Hi Jeff, Richard,
>> Thank you for reviewing the patch!
>> I have committed the patch to the gcc repo.
>> Can I backport this patch to prior versions of gcc, as this is an easy patch to backport and the issue exists in prior versions too?
>
> It doesn't seem to be a regression so I'd error on the safe side here.
Can you please clarify, should this patch be backported? It is not very clear what "safe side" means here.
Thanks!
Surya
>
> Richard.
>
>> Regards,
>> Surya
>>
>>
>> On 31/08/22 9:09 pm, Jeff Law via Gcc-patches wrote:
>>>
>>>
>>> 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-11-08 16:37 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
2022-09-20 7:17 ` Surya Kumari Jangala
2022-09-21 7:33 ` Richard Biener
2022-11-08 16:36 ` Surya Kumari Jangala [this message]
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=be914ec4-3bc7-823d-7317-f07a6d3b3eee@linux.vnet.ibm.com \
--to=jskumari@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).