public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30089] Compiling FreeFem3d uses unreasonable amount of time and memory
Date: Wed, 13 Dec 2006 23:50:00 -0000	[thread overview]
Message-ID: <20061213235016.2792.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30089-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from dnovillo at gcc dot gnu dot org  2006-12-13 23:50 -------

The memory problem is quite simple: We just have a *lot* of pointers and a
*lot* of addressable symbols.  Here is a breakdown of what happens on the first
call to compute_may_aliases:

During the first call to compute_may_aliases:

1- Size of cc1plus is 339Mb
2- Call to compute_points_to_sets grows to 355Mb (+4.72%)
3- Call to compute_flow_insensitive_aliasing grows to 364Mb (+2.54%)
4- Call to compute_flow_sensitive_aliasing grows to 667Mb (+83.2%)

The reason for this tremendous growth is quite simple.  There are 39,010 SSA
name pointers and many of them have their own points-to set, which we store in
that name's may-alias set.  We grow to 667Mb in the last loop of
compute_flow_sensitive_aliasing.

One thing we could do is just not use flow-sensitive information in these
cases.  If we don't set SSA_NAME_PTR_INFO, everything will default to
flow-insensitive information and things will Just Work.

Perhaps using sparse bitmaps for the may-alias sets might help with memory
consumption, but I found these bitmaps to slow down the operand scanner quite a
bit in the past.  May be worth a try.

Danny, thoughts?


-- 


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


  parent reply	other threads:[~2006-12-13 23:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 17:15 [Bug tree-optimization/30089] New: " rguenth at gcc dot gnu dot org
2006-12-06 17:17 ` [Bug tree-optimization/30089] " rguenth at gcc dot gnu dot org
2006-12-06 17:19 ` rguenth at gcc dot gnu dot org
2006-12-06 17:20 ` rguenth at gcc dot gnu dot org
2006-12-07  4:48 ` dberlin at gcc dot gnu dot org
2006-12-07 12:41 ` rguenth at gcc dot gnu dot org
2006-12-07 14:07 ` rguenth at gcc dot gnu dot org
2006-12-12 16:44 ` rguenth at gcc dot gnu dot org
2006-12-13 17:32 ` dnovillo at gcc dot gnu dot org
2006-12-13 23:50 ` dnovillo at gcc dot gnu dot org [this message]
2006-12-13 23:54 ` dnovillo at gcc dot gnu dot org
2006-12-14  1:11 ` dberlin at dberlin dot org
2006-12-14  2:50 ` dnovillo at gcc dot gnu dot org
2006-12-23 14:26 ` hubicka at gcc dot gnu dot org
2006-12-23 14:27 ` hubicka at gcc dot gnu dot org
2006-12-23 16:21 ` dberlin at dberlin dot org
2007-01-09 21:17 ` rguenth at gcc dot gnu dot org
2007-01-09 21:42   ` Daniel Berlin
2007-01-09 21:42 ` dberlin at dberlin dot org
2007-01-10 18:39 ` rguenth at gcc dot gnu dot org
2007-01-11 18:12 ` rguenth at gcc dot gnu dot org
2007-01-13 23:02 ` rguenth at gcc dot gnu dot org
2007-01-14  1:22   ` Daniel Berlin
2007-01-14  1:22 ` dberlin at dberlin dot org
2007-01-14 15:06 ` rguenth at gcc dot gnu dot org
2007-03-30 15:59 ` dberlin at gcc dot gnu dot org
2007-03-31 13:42 ` rguenth at gcc dot gnu dot org
2007-03-31 13:43 ` [Bug tree-optimization/30089] [4.3 Regression] " rguenth at gcc dot gnu dot 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=20061213235016.2792.qmail@sourceware.org \
    --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).