public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/29587] jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes Date: Tue, 07 Nov 2006 17:40:00 -0000 [thread overview] Message-ID: <20061107174024.9712.qmail@sourceware.org> (raw) In-Reply-To: <bug-29587-276@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from dberlin at gcc dot gnu dot org 2006-11-07 17:40 ------- Subject: Re: jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes On 6 Nov 2006 00:43:29 -0000, dave at hiauly1 dot hia dot nrc dot ca <gcc-bugzilla@gcc.gnu.org> wrote: > > > ------- Comment #9 from dave at hiauly1 dot hia dot nrc dot ca 2006-11-06 00:43 ------- > Subject: Re: jc1: out of memory allocating 4072 bytes after a total of > 708630224 bytes > > > So this ends up being what i thought. The variables aren't being > > collapsed, but i can't figure out why (IE it can't prove they are the > > same). This causes it to give them separate solution bitmaps, and the > > solutions are very large,and involve thousands of variables, so > > thousands * thousands = a lot of memory. > > It appears that every one of them has its address taken. The code > skips such variables: > > /* We can't eliminate things whose address is taken, or which is > the target of a dereference. */ > if (vi->address_taken || vi->indirect_target) > continue; > > > However, all of these variables should collapse, as they do in the > > earlier functions. > > For the record, I believe we die processing this constructor function: > > ;; Function _GLOBAL__I_0__ZN3gnu3xml8aelfred215XmlParser$InputC1Ev() > (_GLOBAL__I > _0__ZN3gnu3xml8aelfred215XmlParser$InputC1Ev) > > The alias1 files has the following: > > ... > ESCAPED_VARS = &gnu.xml.xpath.AndExpr.class$$.engine > > Collapsing static cycles and doing variable substitution: > > Solving graph: > > Dave > > I agree with your assessment, I will fix it so they all collapse again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29587
next prev parent reply other threads:[~2006-11-07 17:40 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-24 23:06 [Bug java/29587] New: " danglin at gcc dot gnu dot org 2006-10-31 11:06 ` [Bug java/29587] " r dot emrich at de dot tecosim dot com 2006-10-31 15:39 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-04 15:47 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-04 17:45 ` dberlin at dberlin dot org 2006-11-04 22:07 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-05 19:16 ` dberlin at gcc dot gnu dot org 2006-11-05 21:22 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-05 21:48 ` dberlin at dberlin dot org 2006-11-06 0:43 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-07 17:40 ` dberlin at dberlin dot org [this message] 2006-11-09 17:24 ` dberlin at dberlin dot org 2006-11-10 15:20 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-13 2:18 ` dberlin at gcc dot gnu dot org 2006-11-13 2:22 ` dberlin at gcc dot gnu dot org 2006-11-13 2:22 ` dberlin at gcc dot gnu dot org 2006-11-13 2:31 ` dave at hiauly1 dot hia dot nrc dot ca 2006-12-01 1:04 ` chaoyingfu at gcc dot gnu dot org 2007-02-22 3:26 ` van at wdv dot com 2007-10-12 9:56 ` cnstar9988 at gmail 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=20061107174024.9712.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).