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 rtl-optimization/114261] [13/14 Regression] Scheduling takes excessive time (97%) since r13-5154-g733a1b777f1
Date: Tue, 12 Mar 2024 07:49:43 +0000	[thread overview]
Message-ID: <bug-114261-4-LupVNrqRcE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114261-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Isn't the "scheduling window" limited somehow?  Can we impose an upper bound on
the number of dependences by placing a "virtual barrier" when we hit that
limit?
I don't know the structure of the scheduler or it's dependence analysis
framework.

In other places where GCC faces this usual quadraticness in dependence analysis
we have such limits and try to cope with it as good as we can, worst give up
completely.

  parent reply	other threads:[~2024-03-12  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  1:37 [Bug rtl-optimization/114261] New: [13/14 Regression] Scheduling takes excessive time (97%) patrick at rivosinc dot com
2024-03-07  1:38 ` [Bug rtl-optimization/114261] " patrick at rivosinc dot com
2024-03-07  1:40 ` pinskia at gcc dot gnu.org
2024-03-07  1:40 ` patrick at rivosinc dot com
2024-03-07  7:30 ` amonakov at gcc dot gnu.org
2024-03-07  7:51 ` patrick at rivosinc dot com
2024-03-07 20:36 ` law at gcc dot gnu.org
2024-03-11 16:30 ` amonakov at gcc dot gnu.org
2024-03-12  7:49 ` rguenth at gcc dot gnu.org [this message]
2024-03-13  3:09 ` [Bug rtl-optimization/114261] [13/14 Regression] Scheduling takes excessive time (97%) since r13-5154-g733a1b777f1 law at gcc dot gnu.org
2024-03-13 13:56 ` amonakov at gcc dot gnu.org
2024-03-13 14:08 ` rguenth at gcc dot gnu.org
2024-03-13 15:11 ` amonakov 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-114261-4-LupVNrqRcE@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).