From: Richard Biener <richard.guenther@gmail.com>
To: Giuliano Belinassi <giuliano.belinassi@usp.br>,
Jan Hubicka <hubicka@ucw.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
gold@ime.usp.br, Gregory.Mounie@imag.fr
Subject: Re: [PATCH] Wrap 'expand_all_functions' and 'ipa_passes' around timevars
Date: Mon, 28 Jan 2019 12:04:00 -0000 [thread overview]
Message-ID: <CAFiYyc0a2dFsE8wWyCej6+6j87O78RJWpqw9y7MSc5Hd1MJ-bA@mail.gmail.com> (raw)
In-Reply-To: <20190124195117.ozr7i6s2cptp37s3@smtp.gmail.com>
On Thu, Jan 24, 2019 at 8:51 PM Giuliano Belinassi
<giuliano.belinassi@usp.br> wrote:
>
> This patch adds two variables named 'TV_CGRAPH_FUNC_EXPANSION' and
> 'TV_CGRAPH_IPA_PASSES' that count the elapsed time of the functions
> 'expand_all_functions' and 'ipa_passes', respectivelly.
>
> The main point of this is that these functions takes a very long time
> when compiling the 'gimple-match.c' file, and therefore may also take
> a long time when compiling other large files.
But as implemented those shouldn't accumulate a lot of time because other
timevars are pushed for them.
I think you want to instead split TV_PHASE_OPT_GEN into
TV_PHASE_OPT_GIMPLE TV_PHASE_IPA and TV_PHASE_RTL
which probably can be easiest managed by the pass manager
pushing/popping those appropriately depending on the pass kind
that is invoked?
Richard.
> I also accept suggestions about how to improve this :-)
>
> ChangeLog:
>
> 2019-01-24 Giuliano Belinassi <giuliano.belinassi@usp.br>
>
> * cgraph_unit.c (compile): TV_CGRAPH_FUNC_EXPANSION and
> TV_CGRAPH_IPA_PASSES start, stop.
> * timevar.def (TV_CGRAPH_IPA_PASSES, TV_CGRAPH_FUNC_EXPANSION): New.
>
>
next prev parent reply other threads:[~2019-01-28 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 19:53 Giuliano Belinassi
2019-01-28 12:04 ` Richard Biener [this message]
2019-01-28 13:29 ` Giuliano Belinassi
2019-01-28 15:33 ` Richard Biener
2019-06-19 18:34 ` Jeff Law
2019-06-19 20:27 ` Giuliano Belinassi
2019-06-20 22:47 ` Jeff Law
2019-07-03 2:56 ` Jeff Law
2019-07-03 14:13 ` Giuliano Belinassi
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=CAFiYyc0a2dFsE8wWyCej6+6j87O78RJWpqw9y7MSc5Hd1MJ-bA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=Gregory.Mounie@imag.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=giuliano.belinassi@usp.br \
--cc=gold@ime.usp.br \
--cc=hubicka@ucw.cz \
/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).