public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30052] [4.2 Regression] points-to analysis slow and memory hungry
Date: Wed, 11 Jun 2008 08:08:00 -0000	[thread overview]
Message-ID: <20080611080755.25228.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30052-7667@http.gcc.gnu.org/bugzilla/>



------- Comment #61 from rguenther at suse dot de  2008-06-11 08:07 -------
Subject: Re:  [4.2 Regression] points-to analysis
 slow and memory hungry

On Tue, 10 Jun 2008, giovannibajo at libero dot it wrote:

> ------- Comment #60 from giovannibajo at libero dot it  2008-06-10 17:26 -------
> If a knowledgable GCC developer could suggest *any* workaround at -O1 for this
> bug in 4.2 (including disabling whatever alias analysys causes the problem), it
> might be proposed as a fix within distros at least.

You can try if --param max-fields-for-field-sensitive=0 improves the
situation.

Other than that, try, in 
tree-ssa-structalias.c:create_variable_info_for remove the
make_constraint_from_escaped and make_constraint_to_escaped calls for
the is_global cases.  Note that you need to adjust find_what_p_points_to
to include escaped variables if escaped_id is set in the solution and
that call clobbering will need similar adjustments (and remember
escaped_id includes all globals implicitly).  The problem with the
sipQt testcase is that it has 10000s of global vars it creates
constraints for, even though they are unused.

Richard. 


-- 


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


      parent reply	other threads:[~2008-06-11  8:08 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 17:57 [Bug target/30052] New: memory hog pluto at agmk dot net
2006-12-02 17:58 ` [Bug target/30052] " pluto at agmk dot net
2006-12-06 13:24 ` [Bug target/30052] memory hog on x86-64 pluto at agmk dot net
2007-01-02 20:34 ` pluto at agmk dot net
2007-01-10 19:58 ` pluto at agmk dot net
2007-01-14  0:54 ` arekm at pld-linux dot org
2007-02-12 18:25 ` pluto at agmk dot net
2007-02-12 18:27 ` pluto at agmk dot net
2007-02-12 20:47 ` [Bug target/30052] possible quadratic behaviour dberlin at gcc dot gnu dot org
2007-02-13 10:38 ` pluto at agmk dot net
2007-02-13 16:17 ` dberlin at dberlin dot org
2007-02-14  8:18 ` pluto at agmk dot net
2007-03-14 14:15 ` rguenth at gcc dot gnu dot org
2007-03-14 14:21 ` [Bug target/30052] [4.2 Regression] " rguenth at gcc dot gnu dot org
2007-03-14 15:12 ` dberlin at gcc dot gnu dot org
2007-04-25 20:56 ` pluto at agmk dot net
2007-04-26  1:20 ` dberlin at dberlin dot org
2007-05-02 20:42 ` mmitchel at gcc dot gnu dot org
2007-05-14 19:05 ` pluto at agmk dot net
2007-05-18  9:15 ` rguenth at gcc dot gnu dot org
2007-05-18 13:47 ` dberlin at gcc dot gnu dot org
2007-05-18 14:51 ` [Bug tree-optimization/30052] " rguenth at gcc dot gnu dot org
2007-05-18 22:31 ` m dot vegni at it-systems dot it
2007-05-19 14:30 ` pluto at agmk dot net
2007-05-19 16:29   ` Daniel Berlin
2007-05-19 16:30 ` dberlin at dberlin dot org
2007-05-19 17:16 ` pluto at agmk dot net
2007-05-19 17:43   ` Daniel Berlin
2007-05-19 17:43 ` dberlin at dberlin dot org
2007-05-20  4:58 ` pluto at agmk dot net
2007-05-20 22:52   ` Daniel Berlin
2007-05-20 22:52 ` dberlin at dberlin dot org
2007-05-21 16:01 ` pluto at agmk dot net
2007-05-21 16:53 ` dberlin at dberlin dot org
2007-06-03  7:21 ` pluto at agmk dot net
2007-06-08 23:38 ` pinskia at gcc dot gnu dot org
2007-06-11 13:05 ` pluto at agmk dot net
2007-06-11 13:07 ` rguenther at suse dot de
2007-06-11 13:17 ` pluto at agmk dot net
2007-06-11 14:04 ` pluto at agmk dot net
2007-06-11 14:08 ` rguenth at gcc dot gnu dot org
2007-06-11 14:11 ` pluto at agmk dot net
2007-06-11 14:15 ` rguenth at gcc dot gnu dot org
2007-06-11 14:17 ` [Bug tree-optimization/30052] [4.2/4.3 " rguenth at gcc dot gnu dot org
2007-06-11 15:40 ` dberlin at dberlin dot org
2007-07-20  3:48 ` [Bug tree-optimization/30052] [4.2/4.3 Regression] points-to analysis slow and memory hungry mmitchel at gcc dot gnu dot org
2007-07-26 11:20 ` debian-gcc at lists dot debian dot org
2007-07-26 18:03 ` dberlin at gcc dot gnu dot org
2007-09-11 10:59 ` giovannibajo at libero dot it
2007-09-11 12:58 ` dberlin at dberlin dot org
2007-09-11 19:51 ` belyshev at depni dot sinp dot msu dot ru
2007-09-11 19:54 ` dberlin at dberlin dot org
2007-09-11 19:55 ` [Bug tree-optimization/30052] [4.2 " dberlin at gcc dot gnu dot org
2007-10-09 11:44 ` rguenth at gcc dot gnu dot org
2007-10-09 19:26 ` mmitchel at gcc dot gnu dot org
2008-02-01 16:56 ` jsm28 at gcc dot gnu dot org
2008-03-12 11:19 ` chkr at plauener dot de
2008-03-12 12:13 ` rguenth at gcc dot gnu dot org
2008-03-12 12:14 ` rguenther at suse dot de
2008-05-21 14:19 ` rguenth at gcc dot gnu dot org
2008-05-21 15:50 ` giovannibajo at libero dot it
2008-05-21 15:52 ` rguenth at gcc dot gnu dot org
2008-05-21 16:06 ` rguenth at gcc dot gnu dot org
2008-05-21 16:08 ` rguenth at gcc dot gnu dot org
2008-06-10 17:27 ` giovannibajo at libero dot it
2008-06-11  8:08 ` rguenther at suse dot de [this message]

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=20080611080755.25228.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).