public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, CPROP, PRE and LRA passes
Date: Fri, 29 Jan 2021 15:56:21 +0000 [thread overview]
Message-ID: <bug-98863-4-y6QjTBgEp7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98863-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98863
--- Comment #28 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Biener from comment #27)
> HJ, you added remove_partial_avx_dependency - it adds loads of DF problems
> but during its execution it does not seem to use anything but doing
> df_insn_rescan. I'm not too familiar with DF so I assume calling
> df_analyze is necessary to mark insns for rescan (I'd assume _not_ calling
> df_analyze but only setting defered-rescan and not processing defered
> rescans in a pass not needing DF at all should work?! Or even defered
> rescan is default on in that case).
>
> Besides this the pass ups memory use from 2GB to 7GB and memory use doesn't
> drop so there's sth fishy going on here.
>
> I'm testing the obvious remove of
>
> df_chain_add_problem (DF_DU_CHAIN | DF_UD_CHAIN);
> df_md_add_problem ();
>
> which was likely copied from STV (where I removed adding MD), but STV
> _does_ at least use DF and exercises use/def chains.
>
> I'm also not sure altering the CFG is the very best thing to do when
> DF is active (and doing that with MD or DU/UD might cause interesting
> unknown issues I guess). At least with not adding MD or DU/UD_CHAIN
> the "leak" is gone. Richard or Jakub may know more here, esp. whether
> we can elide the df_analyze completely (I hope we can!). Even
> DF_LIVE and LR alone are a major hog on this testcase (but at least
> stay within 2GB of memory while RD tops at 7GB).
If it isn't used, please remove it.
next prev parent reply other threads:[~2021-01-29 15:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 11:19 [Bug rtl-optimization/98863] New: WRF with LTO consumes a lot of memory in split2 pass marxin at gcc dot gnu.org
2021-01-28 11:20 ` [Bug rtl-optimization/98863] " marxin at gcc dot gnu.org
2021-01-28 13:18 ` rguenth at gcc dot gnu.org
2021-01-28 13:21 ` marxin at gcc dot gnu.org
2021-01-28 14:14 ` marxin at gcc dot gnu.org
2021-01-28 14:20 ` rguenth at gcc dot gnu.org
2021-01-28 14:24 ` rguenth at gcc dot gnu.org
2021-01-28 15:09 ` marxin at gcc dot gnu.org
2021-01-28 15:15 ` rguenth at gcc dot gnu.org
2021-01-28 15:17 ` rguenth at gcc dot gnu.org
2021-01-28 15:18 ` rguenth at gcc dot gnu.org
2021-01-28 15:30 ` rguenth at gcc dot gnu.org
2021-01-29 8:47 ` rguenth at gcc dot gnu.org
2021-01-29 9:03 ` rguenth at gcc dot gnu.org
2021-01-29 9:47 ` rguenth at gcc dot gnu.org
2021-01-29 9:56 ` marxin at gcc dot gnu.org
2021-01-29 10:18 ` marxin at gcc dot gnu.org
2021-01-29 10:24 ` rguenther at suse dot de
2021-01-29 11:03 ` rguenth at gcc dot gnu.org
2021-01-29 11:03 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE pass rguenth at gcc dot gnu.org
2021-01-29 11:38 ` marxin at gcc dot gnu.org
2021-01-29 12:13 ` rguenth at gcc dot gnu.org
2021-01-29 12:50 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, CPROP, PRE and LRA passes rguenth at gcc dot gnu.org
2021-01-29 12:57 ` marxin at gcc dot gnu.org
2021-01-29 13:01 ` cvs-commit at gcc dot gnu.org
2021-01-29 13:23 ` rguenth at gcc dot gnu.org
2021-01-29 13:37 ` marxin at gcc dot gnu.org
2021-01-29 14:39 ` rguenth at gcc dot gnu.org
2021-01-29 15:01 ` rguenth at gcc dot gnu.org
2021-01-29 15:56 ` hjl.tools at gmail dot com [this message]
2021-01-29 16:32 ` cvs-commit at gcc dot gnu.org
2021-02-01 8:22 ` cvs-commit at gcc dot gnu.org
2021-02-01 9:31 ` marxin at gcc dot gnu.org
2021-02-01 10:41 ` rguenth at gcc dot gnu.org
2021-02-01 12:07 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, FWPROP and x86 specific passes rguenth at gcc dot gnu.org
2021-02-01 12:30 ` rsandifo at gcc dot gnu.org
2021-02-01 12:32 ` rguenth at gcc dot gnu.org
2021-02-01 12:45 ` [Bug rtl-optimization/98863] [11 Regression] " rguenth at gcc dot gnu.org
2021-02-01 13:35 ` cvs-commit at gcc dot gnu.org
2021-02-03 10:27 ` cvs-commit at gcc dot gnu.org
2021-02-03 12:33 ` cvs-commit at gcc dot gnu.org
2021-02-08 8:45 ` rsandifo at gcc dot gnu.org
2021-02-08 9:01 ` rguenther at suse dot de
2021-02-08 9:23 ` richard.sandiford at arm dot com
2021-02-08 9:46 ` rguenth at gcc dot gnu.org
2021-02-08 12:44 ` rguenth at gcc dot gnu.org
2021-02-09 12:07 ` cvs-commit at gcc dot gnu.org
2021-02-09 12:40 ` rguenth at gcc dot gnu.org
2021-02-10 13:51 ` rguenth at gcc dot gnu.org
2021-02-15 15:06 ` cvs-commit at gcc dot gnu.org
2021-02-15 15:34 ` rsandifo at gcc dot gnu.org
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=bug-98863-4-y6QjTBgEp7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).