public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/80960] [8/9/10/11 Regression] Huge memory use when compiling a very large test case
Date: Wed, 27 Jan 2021 22:15:12 +0000	[thread overview]
Message-ID: <bug-80960-4-51wy3eyrSk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80960-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #26 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #23)
> (that combine number prevails on trunk as well, I can't spot any code
> that disables combine on large BBs so not sure what goes on here)

There is no such thing, indeed.  And the instruction combiner is
"mostly linear", so it shouldn't actually matter.

  parent reply	other threads:[~2021-01-27 22:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-80960-4@http.gcc.gnu.org/bugzilla/>
2021-01-27 12:23 ` rguenth at gcc dot gnu.org
2021-01-27 13:09 ` rguenth at gcc dot gnu.org
2021-01-27 14:35 ` rguenth at gcc dot gnu.org
2021-01-27 22:15 ` segher at gcc dot gnu.org [this message]
2021-01-28  8:14 ` cvs-commit at gcc dot gnu.org
2021-01-29 11:05 ` [Bug rtl-optimization/80960] [8/9/10 " rguenth at gcc dot gnu.org
2021-05-14  9:49 ` [Bug rtl-optimization/80960] [9/10 " jakub at gcc dot gnu.org
2021-05-17 17:12 ` cvs-commit at gcc dot gnu.org
2021-05-18  7:05 ` [Bug rtl-optimization/80960] [9 " cvs-commit at gcc dot gnu.org
2021-05-18  7:07 ` 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-80960-4-51wy3eyrSk@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).