From: Alexander Monakov <amonakov@ispras.ru>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
"Kewen.Lin" <linkw@linux.ibm.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>,
Jeff Law <jlaw@ventanamicro.com>,
Vladimir Makarov <vmakarov@redhat.com>,
zhroma@ispras.ru, Andrey Belevantsev <abel@ispras.ru>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
Michael Meissner <meissner@linux.ibm.com>,
Alexandre Oliva <oliva@adacore.com>
Subject: Re: PING^1 [PATCH v3] sched: Change no_real_insns_p to no_real_nondebug_insns_p [PR108273]
Date: Fri, 10 Nov 2023 17:18:31 +0300 (MSK) [thread overview]
Message-ID: <f481b7b6-4ae2-b66d-9670-7b7621f10374@ispras.ru> (raw)
In-Reply-To: <CAFiYyc1gS9NtQ_-DuvsLckBmsuqhNrsF+r4hhHkVLx2sACw2zQ@mail.gmail.com>
On Fri, 10 Nov 2023, Richard Biener wrote:
> > I'm afraid ignoring debug-only BBs goes contrary to overall var-tracking design:
> > DEBUG_INSNs participate in dependency graph so that schedulers can remove or
> > mutate them as needed when moving real insns across them.
>
> Note that debug-only BBs do not exist - the BB would be there even without debug
> insns!
Yep, sorry, I misspoke when I earlier said
>> and cause divergence when passing through a debug-only BB which would not be
>> present at all without -g.
They are present in the region, but skipped via no_real_insns_p.
> So instead you have to handle BBs with just debug insns the same you
> handle a completely empty BB.
Yeah. There would be no problem if the scheduler never used no_real_insns_p
and handled empty and non-empty BBs the same way.
Alexander
next prev parent reply other threads:[~2023-11-10 14:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 2:45 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 [this message]
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
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=f481b7b6-4ae2-b66d-9670-7b7621f10374@ispras.ru \
--to=amonakov@ispras.ru \
--cc=abel@ispras.ru \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jlaw@ventanamicro.com \
--cc=linkw@linux.ibm.com \
--cc=maxim.kuvyrkov@linaro.org \
--cc=meissner@linux.ibm.com \
--cc=oliva@adacore.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.org \
--cc=vmakarov@redhat.com \
--cc=zhroma@ispras.ru \
/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).