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 c++/53226] memory consumption for heavy template instantiations increased massively
Date: Tue, 08 May 2012 12:13:00 -0000	[thread overview]
Message-ID: <bug-53226-4-Vel47sUQ3W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53226-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-08 12:09:05 UTC ---
(In reply to comment #9)
> Ugh, remove_prop_source_from_use can remove stmts while prev iterator points to
> them.  This has been buggy before, but didn't result in endless loop.
> I guess instead of using prev/prev_initialized, the loop could gimple_set_uid
> (stmt, 0) the stmts it is about to process and gimple_set_uid (stmt, 1) stmts
> that don't need to be processed again, then gsi = prev; could be just replaced
> by doing gsi_prev (&gsi); enough times to reach start of bb or a stmt with uid
> 1.

The other way is to try to get away without immediately removing propagated
source stmts - the obvious downside is that transforms relying on
single-use definitions will be confused by those dead uses (but the scheme
how it works now is fragile anyway because we are not sure we visit the stmts
in the correct order).


  parent reply	other threads:[~2012-05-08 12:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04  7:10 [Bug c++/53226] New: " mario-baumann at web dot de
2012-05-04  7:22 ` [Bug c++/53226] " manu at gcc dot gnu.org
2012-05-04  9:01 ` rguenth at gcc dot gnu.org
2012-05-04  9:33 ` mario-baumann at web dot de
2012-05-04 19:52 ` mario-baumann at web dot de
2012-05-08  7:15 ` mario-baumann at web dot de
2012-05-08  7:55 ` mario-baumann at web dot de
2012-05-08 10:16 ` rguenth at gcc dot gnu.org
2012-05-08 12:04 ` matz at gcc dot gnu.org
2012-05-08 12:10 ` jakub at gcc dot gnu.org
2012-05-08 12:13 ` rguenth at gcc dot gnu.org [this message]
2012-05-08 12:13 ` matz at gcc dot gnu.org
2012-05-08 13:20 ` rguenth at gcc dot gnu.org
2012-05-08 13:25 ` matz at gcc dot gnu.org
2012-05-08 16:36 ` [Bug tree-optimization/53226] [4.8 Regression] Endless loop in forwprop jakub at gcc dot gnu.org
2012-05-09 12:22 ` jakub at gcc dot gnu.org
2012-05-09 12:33 ` jakub 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-53226-4-Vel47sUQ3W@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).