public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/40761] IRA memory hog for insanely nested loops
Date: Thu, 19 Jan 2012 20:50:00 -0000	[thread overview]
Message-ID: <bug-40761-4-nLIU8XKCDl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40761-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40761

--- Comment #17 from Vladimir Makarov <vmakarov at redhat dot com> 2012-01-19 20:42:57 UTC ---
  The problem was in building CFG loops which took the most of time.   CFG
loops were built even if we don't use regional allocation as for -O0.

  I'll send a patch soon.  It is not small because IRA in any case uses one
region with CFG loop representing the whole function.


  parent reply	other threads:[~2012-01-19 20:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40761-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 13:24 ` [Bug rtl-optimization/40761] [4.4/4.5/4.6 Regression] " rguenth at gcc dot gnu.org
2011-04-28 15:45 ` [Bug rtl-optimization/40761] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-16 14:34 ` [Bug rtl-optimization/40761] " rguenth at gcc dot gnu.org
2012-01-19  0:25 ` vmakarov at redhat dot com
2012-01-19 20:50 ` vmakarov at redhat dot com [this message]
2012-01-19 21:07 ` vmakarov at gcc dot gnu.org
2012-04-27  3:13 ` law at redhat dot com

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-40761-4-nLIU8XKCDl@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).