From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Alexander Monakov <amonakov@ispras.ru>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: PING^1 [PATCH] sched: Remove debug counter sched_block
Date: Thu, 21 Dec 2023 13:46:04 +0800 [thread overview]
Message-ID: <37b2c4f1-62d9-9e87-67e7-91c3ab38968d@linux.ibm.com> (raw)
In-Reply-To: <658c398c-6eb9-4567-ab8c-e97f188a9590@gmail.com>
Hi Jeff,
on 2023/12/21 04:43, Jeff Law wrote:
>
>
> On 12/11/23 23:17, Kewen.Lin wrote:
>> Hi,
>>
>> Gentle ping this:
>>
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636597.html
>>
>> BR,
>> Kewen
>>
>> on 2023/11/15 17:01, Kewen.Lin wrote:
>>> Hi,
>>>
>>> on 2023/11/10 01:40, Alexander Monakov wrote:
>>>
>>>> I agree with the concern. I hoped that solving the problem by skipping the BB
>>>> like the (bit-rotted) debug code needs to would be a minor surgery. As things
>>>> look now, it may be better to remove the non-working sched_block debug counter
>>>> entirely and implement a good solution for the problem at hand.
>>>>
>>>
>>> According to this comment, I made and tested the below patch to remove the
>>> problematic debug counter:
>>>
>>> Subject: [PATCH] sched: Remove debug counter sched_block
>>>
>>> Currently the debug counter sched_block doesn't work well
>>> since we create dependencies for some insns and those
>>> dependencies are expected to be resolved during scheduling
>>> insns but they can get skipped once we are skipping some
>>> block while respecting sched_block debug counter.
>>>
>>> For example, for the below test case:
>>> --
>>> int a, b, c, e, f;
>>> float d;
>>>
>>> void
>>> g ()
>>> {
>>> float h, i[1];
>>> for (; f;)
>>> if (c)
>>> {
>>> d *e;
>>> if (b)
>>> {
>>> float *j = i;
>>> j[0] = 0;
>>> }
>>> h = d;
>>> }
>>> if (h)
>>> a = i[0];
>>> }
>>> --
>>> ICE occurs with option "-O2 -fdbg-cnt=sched_block:1".
>>>
>>> As the discussion in [1], it seems that we think this debug
>>> counter is useless and can be removed. It's also implied
>>> that if it's useful and used often, the above issue should
>>> have been cared about and resolved earlier. So this patch
>>> is to remove this debug counter.
>>>
>>> Bootstrapped and regtested on x86_64-redhat-linux and
>>> powerpc64{,le}-linux-gnu.
>>>
>>> [1] https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635852.html
>>>
>>> Is it ok for trunk?
>>>
>>> BR,
>>> Kewen
>>> -----
>>>
>>> gcc/ChangeLog:
>>>
>>> * dbgcnt.def (sched_block): Remove.
>>> * sched-rgn.cc (schedule_region): Remove the support of debug count
>>> sched_block.
> OK. SOrry about the delay.
Thanks for the review, pushed as r14-6766-gef259ebeb39501.
BR,
Kewen
prev parent reply other threads:[~2023-12-21 5:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 2:45 [PATCH v3] sched: Change no_real_insns_p to no_real_nondebug_insns_p [PR108273] Kewen.Lin
2023-11-08 2:49 ` PING^1 " Kewen.Lin
2023-11-08 9:45 ` Richard Sandiford
2023-11-09 9:10 ` Maxim Kuvyrkov
2023-11-09 17:40 ` Alexander Monakov
2023-11-10 1:57 ` Kewen.Lin
2023-11-10 3:49 ` Jeff Law
2023-11-10 11:25 ` Alexander Monakov
2023-11-10 13:32 ` Richard Biener
2023-11-10 14:18 ` Alexander Monakov
2023-11-10 14:20 ` Richard Biener
2023-11-10 14:41 ` Alexander Monakov
2023-11-15 9:12 ` Kewen.Lin
2023-11-15 9:43 ` Alexander Monakov
2023-11-17 9:03 ` Kewen.Lin
2023-11-17 10:13 ` Richard Biener
2023-11-17 12:55 ` Alexander Monakov
2023-11-22 9:30 ` Kewen.Lin
2023-11-22 10:25 ` Richard Biener
2023-11-23 2:36 ` Kewen.Lin
2023-11-23 8:20 ` Richard Biener
2023-11-23 9:09 ` Kewen.Lin
2023-12-12 7:02 ` [PATCH draft v2] sched: Don't skip empty block in scheduling [PR108273] Kewen.Lin
2023-11-10 3:49 ` PING^1 [PATCH v3] sched: Change no_real_insns_p to no_real_nondebug_insns_p [PR108273] Jeff Law
2023-11-15 9:01 ` [PATCH] sched: Remove debug counter sched_block Kewen.Lin
2023-12-12 6:17 ` PING^1 " Kewen.Lin
2023-12-20 20:43 ` Jeff Law
2023-12-21 5:46 ` Kewen.Lin [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=37b2c4f1-62d9-9e87-67e7-91c3ab38968d@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=maxim.kuvyrkov@linaro.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).