public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114729] RISC-V SPEC2017 507.cactu excessive spillls with -fschedule-insns
Date: Tue, 16 Apr 2024 13:58:18 +0000	[thread overview]
Message-ID: <bug-114729-4-dUbesSycdq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114729-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jeffrey A. Law <law at gcc dot gnu.org> ---
I didn't even notice you had that testcase attached!

I haven't done a deep dive, but the first thing that jumps out is the number of
instructions in the ready queue, most likely because of the addressing of
objects in static storage.  The highparts alone are going to take ~18 GPRs for
the loop.

  parent reply	other threads:[~2024-04-16 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 22:42 [Bug target/114729] New: " vineetg at gcc dot gnu.org
2024-04-15 22:43 ` [Bug rtl-optimization/114729] " pinskia at gcc dot gnu.org
2024-04-15 22:49 ` vineetg at gcc dot gnu.org
2024-04-15 23:14 ` law at gcc dot gnu.org
2024-04-15 23:28 ` vineetg at gcc dot gnu.org
2024-04-16  2:39 ` juzhe.zhong at rivai dot ai
2024-04-16  7:40 ` rguenth at gcc dot gnu.org
2024-04-16 13:49 ` law at gcc dot gnu.org
2024-04-16 13:58 ` law at gcc dot gnu.org [this message]
2024-04-16 23:02 ` vineetg at gcc dot gnu.org
2024-04-18  0:45 ` vineetg at gcc dot gnu.org
2024-04-18 14:30 ` law at gcc dot gnu.org
2024-06-17 20:53 ` vineetg 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-114729-4-dUbesSycdq@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).