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/63577] [4.8/4.9/5 Regression]: Huge compile time and memory usage with -O and not -fPIC
Date: Wed, 28 Jan 2015 02:46:00 -0000	[thread overview]
Message-ID: <bug-63577-4-UFUWABntRl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63577-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
[ I missed your last comment, sorry. ]

Both the log_links and the reg_stat point to insns in the insn stream,
(all of those are either live or never again referred to), so that
might be fine, but you really should make sure you only GC between
try_combine calls, never inside one -- that would be rather disastrous.

Do you want to try this for GCC 5?


  parent reply	other threads:[~2015-01-28  2:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 14:59 [Bug fortran/63577] New: [4.8/4.9/5? " jfsoden at mpp dot mpg.de
2014-10-20 13:06 ` [Bug rtl-optimization/63577] " rguenth at gcc dot gnu.org
2014-10-20 13:08 ` [Bug rtl-optimization/63577] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2014-10-20 18:07 ` segher at gcc dot gnu.org
2014-11-24 13:37 ` rguenth at gcc dot gnu.org
2014-12-19 13:35 ` jakub at gcc dot gnu.org
2015-01-12 14:42 ` jakub at gcc dot gnu.org
2015-01-28  2:46 ` segher at gcc dot gnu.org [this message]
2015-01-28  7:42 ` jakub at gcc dot gnu.org
2015-01-28 20:30 ` segher at gcc dot gnu.org
2015-01-28 20:41 ` jakub at gcc dot gnu.org
2015-01-31 20:19 ` segher 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-63577-4-UFUWABntRl@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).