public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108738] compile-time and memory-hog in mdreorg
Date: Thu, 02 Mar 2023 11:38:59 +0000	[thread overview]
Message-ID: <bug-108738-4-SjeFNJsAl9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108738-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108738

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
So it's now better than before but still quadratic.

Finding a strathegic place to limit the search with some --param might be a
solution, but there's no easy
point to hook that into.  You'd not want to disable the whole pass but
terminate the greedy search and axe the candidates sofar processed (to not run
into the same ones again), which might then result in "odd" STV decisions if
the remains are picked up.  To avoid this maybe maintain a "too big" set of
candidates
and if a further greedy search lands at a insn in that set, axe that search as
well.  Note it's not the size of the set but the complexity of the search that
needs limiting, so count the number of ref visits through
analyze_register_chain
for an invocation of scalar_chain::build and limit that to some --param.

I'm trying to prototype that.

  parent reply	other threads:[~2023-03-02 11:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  8:10 [Bug target/108738] New: " rguenth at gcc dot gnu.org
2023-02-09  8:47 ` [Bug target/108738] " rguenth at gcc dot gnu.org
2023-02-09  9:11 ` rguenth at gcc dot gnu.org
2023-02-09  9:24 ` rguenth at gcc dot gnu.org
2023-02-09 12:48 ` rguenth at gcc dot gnu.org
2023-02-15  7:28 ` cvs-commit at gcc dot gnu.org
2023-02-15  7:28 ` cvs-commit at gcc dot gnu.org
2023-03-02 11:38 ` rguenth at gcc dot gnu.org [this message]
2023-03-03  7:31 ` cvs-commit at gcc dot gnu.org
2023-03-03  7:33 ` rguenth 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-108738-4-SjeFNJsAl9@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).