public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/32723] [4.2 Regression] memory hog in solve_graph Date: Wed, 31 Oct 2007 13:08:00 -0000 [thread overview] Message-ID: <20071031130757.7593.qmail@sourceware.org> (raw) In-Reply-To: <bug-32723-14802@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from rguenth at gcc dot gnu dot org 2007-10-31 13:07 ------- The memory is temporarily needed now by solve_graph(), because the graph has 48902 nodes. On the mainline we have only 3 constraints while for 4.2 we have thousands: ANYTHING = &ANYTHING READONLY = &ANYTHING INTEGER = &ANYTHING ESCAPED_VARS = *ESCAPED_VARS NONLOCAL.6 = ESCAPED_VARS ESCAPED_VARS = &NONLOCAL.6 ESCAPED_VARS = &NONLOCAL.6 infos = ESCAPED_VARS c_20089 = ESCAPED_VARS ESCAPED_VARS = &c_20089 c_20089 = &ANYTHING c_20089 = &ANYTHING ESCAPED_VARS = &c_20089.val c_20089.val = ESCAPED_VARS infos = &c_20089 infos = &c_20089.val c_200A2 = ESCAPED_VARS ESCAPED_VARS = &c_200A2 ... the mainline looks like: ANYTHING = { ANYTHING } READONLY = { ANYTHING } INTEGER = { ANYTHING } D.28988 = same as infos D.28988.c = same as infos D.28988.b = same as infos infos = { ANYTHING } The shared bitmap stuff was not dominant for this testcase. Still I doubt we can backport all of the solver changes. Also quite possibly 4.3 benefits from early optimizations simplifying the problem to solve. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rguenth at gcc dot gnu dot |unassigned at gcc dot gnu |org |dot org Status|REOPENED |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32723
next prev parent reply other threads:[~2007-10-31 13:08 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-10 18:11 [Bug tree-optimization/32723] New: " pixel at mandriva dot com 2007-07-10 18:16 ` [Bug tree-optimization/32723] " pixel at mandriva dot com 2007-07-10 20:23 ` pinskia at gcc dot gnu dot org 2007-07-10 22:21 ` pixel at mandriva dot com 2007-07-11 10:23 ` pixel at mandriva dot com 2007-07-15 20:51 ` pinskia at gcc dot gnu dot org 2007-07-16 9:12 ` rguenth at gcc dot gnu dot org 2007-07-16 9:28 ` rguenth at gcc dot gnu dot org 2007-07-20 3:49 ` mmitchel at gcc dot gnu dot org 2007-07-24 7:16 ` dberlin at gcc dot gnu dot org 2007-07-24 7:31 ` rguenth at gcc dot gnu dot org 2007-07-24 7:31 ` rguenth at gcc dot gnu dot org 2007-08-11 17:08 ` pixel at mandriva dot com 2007-08-20 1:56 ` dberlin at gcc dot gnu dot org 2007-08-21 13:29 ` pixel at mandriva dot com 2007-09-05 0:58 ` mmitchel at gcc dot gnu dot org 2007-10-09 19:27 ` mmitchel at gcc dot gnu dot org 2007-10-31 13:08 ` rguenth at gcc dot gnu dot org [this message] 2007-10-31 14:22 ` dberlin at dberlin dot org 2008-02-01 17:04 ` jsm28 at gcc dot gnu dot org 2008-03-16 17:30 ` rguenth at gcc dot gnu dot org 2008-03-16 17:33 ` 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=20071031130757.7593.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: linkBe 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).