From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: gcc-patches@gcc.gnu.org
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
Vladimir Makarov <vmakarov@redhat.com>,
Jeff Law <jeffreyalaw@gmail.com>,
Alexander Monakov <amonakov@ispras.ru>,
Richard Guenther <richard.guenther@gmail.com>
Subject: Re: [PATCH v3 7/8] Improve logging of register data in scheduler dependency analysis
Date: Mon, 15 Jan 2024 17:06:46 +0400 [thread overview]
Message-ID: <CAD0Vn-BP7DUBR7o66-iizTVRNPyd1RaJSrEDXdA3Kj8DpUcqCQ@mail.gmail.com> (raw)
In-Reply-To: <20231122111415.815147-8-maxim.kuvyrkov@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 5830 bytes --]
Dear scheduler maintainers,
Gentle ping. This patch improves debugging output, it does not touch
scheduling logic.
On Wed, 22 Nov 2023 at 15:15, Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
wrote:
> Scheduler dependency analysis uses two main data structures:
> 1. reg_pending_* data contains effects of INSN on the register file,
> which is then incorporated into ...
> 2. deps_desc object, which contains commulative information about all
> instructions processed from deps_desc object's initialization.
>
> This patch adds debug dumping of (1).
>
> gcc/ChangeLog:
>
> * sched-deps.cc (print-rtl.h): Include for str_pattern_slim().
> (dump_reg_pending_data): New function.
> (sched_analyze_insn): Use it.
> ---
> gcc/sched-deps.cc | 90 ++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 89 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/sched-deps.cc b/gcc/sched-deps.cc
> index e0d3c97d935..f9290c82fd2 100644
> --- a/gcc/sched-deps.cc
> +++ b/gcc/sched-deps.cc
> @@ -38,6 +38,7 @@ along with GCC; see the file COPYING3. If not see
> #include "sched-int.h"
> #include "cselib.h"
> #include "function-abi.h"
> +#include "print-rtl.h"
>
> #ifdef INSN_SCHEDULING
>
> @@ -432,10 +433,24 @@ dep_spec_p (dep_t dep)
> return false;
> }
>
> +/* These regsets describe how a single instruction affects registers.
> + Their "life-time" is restricted to a single call of
> sched_analyze_insn().
> + They are populated by sched_analyze_1() and sched_analyze_2(), and
> + then sched_analyze_insn() transfers data from these into
> deps->reg_last[i].
> + Near the end sched_analyze_insn() clears these regsets for the next
> + insn. */
> static regset reg_pending_sets;
> static regset reg_pending_clobbers;
> static regset reg_pending_uses;
> static regset reg_pending_control_uses;
> +
> +/* Similar to reg_pending_* regsets, this variable specifies whether
> + the current insn analyzed by sched_analyze_insn() is a scheduling
> + barrier that should "split" dependencies inside a block. Internally
> + sched-deps.cc does this by pretending that the barrier insn uses and
> + sets all registers.
> + Near the end sched_analyze_insn() transfers barrier info from this
> variable
> + into deps->last_reg_pending_barrier. */
> static enum reg_pending_barrier_mode reg_pending_barrier;
>
> /* Hard registers implicitly clobbered or used (or may be implicitly
> @@ -2880,7 +2895,77 @@ get_implicit_reg_pending_clobbers (HARD_REG_SET
> *temp, rtx_insn *insn)
> *temp &= ~ira_no_alloc_regs;
> }
>
> -/* Analyze an INSN with pattern X to find all dependencies. */
> +/* Dump state of reg_pending_* data for debug purposes.
> + Dump only non-empty data to reduce log clobber. */
> +static void
> +dump_reg_pending_data (FILE *file, rtx_insn *insn)
> +{
> + fprintf (file, "\n");
> + fprintf (file, ";; sched_analysis after insn %d: %s\n",
> + INSN_UID (insn), str_pattern_slim (PATTERN (insn)));
> +
> + if (!REG_SET_EMPTY_P (reg_pending_sets)
> + || !REG_SET_EMPTY_P (reg_pending_clobbers)
> + || !REG_SET_EMPTY_P (reg_pending_uses)
> + || !REG_SET_EMPTY_P (reg_pending_control_uses))
> + {
> + fprintf (file, ";; insn reg");
> + if (!REG_SET_EMPTY_P (reg_pending_sets))
> + {
> + fprintf (file, " sets(");
> + dump_regset (reg_pending_sets, file);
> + fprintf (file, ")");
> + }
> + if (!REG_SET_EMPTY_P (reg_pending_clobbers))
> + {
> + fprintf (file, " clobbers(");
> + dump_regset (reg_pending_clobbers, file);
> + fprintf (file, ")");
> + }
> + if (!REG_SET_EMPTY_P (reg_pending_uses))
> + {
> + fprintf (file, " uses(");
> + dump_regset (reg_pending_uses, file);
> + fprintf (file, ")");
> + }
> + if (!REG_SET_EMPTY_P (reg_pending_control_uses))
> + {
> + fprintf (file, " control(");
> + dump_regset (reg_pending_control_uses, file);
> + fprintf (file, ")");
> + }
> + fprintf (file, "\n");
> + }
> +
> + if (reg_pending_barrier)
> + fprintf (file, ";; insn reg barrier: %d\n", reg_pending_barrier);
> +
> + if (!hard_reg_set_empty_p (implicit_reg_pending_clobbers)
> + || !hard_reg_set_empty_p (implicit_reg_pending_uses))
> + {
> + fprintf (file, ";; insn reg");
> + if (!hard_reg_set_empty_p (implicit_reg_pending_clobbers))
> + {
> + print_hard_reg_set (file, implicit_reg_pending_clobbers,
> + " implicit clobbers(", false);
> + fprintf (file, ")");
> + }
> + if (!hard_reg_set_empty_p (implicit_reg_pending_uses))
> + {
> + print_hard_reg_set (file, implicit_reg_pending_uses,
> + " implicit uses(", false);
> + fprintf (file, ")");
> + }
> + fprintf (file, "\n");
> + }
> +}
> +
> +/* Analyze an INSN with pattern X to find all dependencies.
> + This analysis uses two main data structures:
> + 1. reg_pending_* data contains effects of INSN on the register file,
> + which is then incorporated into ...
> + 2. deps_desc object, which contains commulative information about all
> + instructions processed from deps_desc object's initialization. */
> static void
> sched_analyze_insn (class deps_desc *deps, rtx x, rtx_insn *insn)
> {
> @@ -3328,6 +3413,9 @@ sched_analyze_insn (class deps_desc *deps, rtx x,
> rtx_insn *insn)
> deps->last_reg_pending_barrier = reg_pending_barrier;
> }
>
> + if (sched_verbose >= 8)
> + dump_reg_pending_data (sched_dump, insn);
> +
> CLEAR_REG_SET (reg_pending_uses);
> CLEAR_REG_SET (reg_pending_clobbers);
> CLEAR_REG_SET (reg_pending_sets);
> --
> 2.34.1
>
>
--
Maxim Kuvyrkov
www.linaro.org
next prev parent reply other threads:[~2024-01-15 13:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 12:06 [PATCH 0/1] Avoid exponential behavior in scheduler and better logging Maxim Kuvyrkov
2023-11-20 12:06 ` [PATCH 1/1] sched-deps.cc (find_modifiable_mems): Avoid exponential behavior Maxim Kuvyrkov
2023-11-20 13:09 ` Richard Biener
2023-11-20 13:42 ` Maxim Kuvyrkov
2023-11-20 13:45 ` Richard Biener
2023-11-20 14:48 ` [PATCH v2] " Maxim Kuvyrkov
2023-11-20 18:59 ` [PATCH 1/1] " Maxim Kuvyrkov
2023-11-20 13:52 ` Alexander Monakov
2023-11-20 14:39 ` Maxim Kuvyrkov
2023-11-20 16:30 ` Alexander Monakov
2023-11-21 10:32 ` Maxim Kuvyrkov
2023-11-21 11:05 ` Alexander Monakov
2023-11-22 11:14 ` [PATCH v3 0/8] Avoid exponential behavior in scheduler and better logging Maxim Kuvyrkov
2023-11-22 11:14 ` [PATCH v3 1/8] sched-deps.cc (find_modifiable_mems): Avoid exponential behavior Maxim Kuvyrkov
2024-01-15 12:56 ` Maxim Kuvyrkov
2024-01-15 18:26 ` Vladimir Makarov
2024-01-16 14:52 ` Jeff Law
2024-01-17 6:51 ` Richard Biener
2024-01-17 7:39 ` Maxim Kuvyrkov
2024-01-17 15:02 ` Richard Biener
2024-01-17 15:05 ` Maxim Kuvyrkov
2024-01-17 15:44 ` Maxim Kuvyrkov
2024-01-17 18:54 ` H.J. Lu
2023-11-22 11:14 ` [PATCH v3 2/8] Unify implementations of print_hard_reg_set() Maxim Kuvyrkov
2023-11-22 15:04 ` Vladimir Makarov
2023-11-22 11:14 ` [PATCH v3 3/8] Simplify handling of INSN_ and EXPR_LISTs in sched-rgn.cc Maxim Kuvyrkov
2024-01-15 12:59 ` Maxim Kuvyrkov
2023-11-22 11:14 ` [PATCH v3 4/8] Improve and fix sched-deps.cc: dump_dep() and dump_lists() Maxim Kuvyrkov
2024-01-15 13:01 ` Maxim Kuvyrkov
2023-11-22 11:14 ` [PATCH v3 5/8] Add a bit more logging scheduler's dependency analysis Maxim Kuvyrkov
2024-01-15 13:04 ` Maxim Kuvyrkov
2023-11-22 11:14 ` [PATCH v3 6/8] sched_deps.cc: Simplify initialization of dependency contexts Maxim Kuvyrkov
2024-01-15 13:05 ` Maxim Kuvyrkov
2023-11-22 11:14 ` [PATCH v3 7/8] Improve logging of register data in scheduler dependency analysis Maxim Kuvyrkov
2024-01-15 13:06 ` Maxim Kuvyrkov [this message]
2023-11-22 11:14 ` [PATCH v3 8/8] Improve logging of scheduler dependency analysis context Maxim Kuvyrkov
2024-01-15 13:08 ` Maxim Kuvyrkov
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=CAD0Vn-BP7DUBR7o66-iizTVRNPyd1RaJSrEDXdA3Kj8DpUcqCQ@mail.gmail.com \
--to=maxim.kuvyrkov@linaro.org \
--cc=amonakov@ispras.ru \
--cc=bernds_cb1@t-online.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=vmakarov@redhat.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).