public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/29587] jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes
Date: Sun, 05 Nov 2006 21:48:00 -0000	[thread overview]
Message-ID: <20061105214810.28911.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29587-276@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from dberlin at gcc dot gnu dot org  2006-11-05 21:48 -------
Subject: Re:  jc1: out of memory allocating 4072 bytes after a total of
708630224 bytes

On 5 Nov 2006 21:22:24 -0000, dave at hiauly1 dot hia dot nrc dot ca
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #7 from dave at hiauly1 dot hia dot nrc dot ca  2006-11-05 21:22 -------
> Subject: Re:  jc1: out of memory allocating 4072 bytes after a total of
> 708630224 bytes
>
> > Can you bzip2 compress -fdump-tree-alias-vops-details-blocks-stats (it's going
> > to be very large) and put it somewhere for me?
>
> The files are here: <ftp://hiauly1.hia.nrc.ca/outgoing/berlin/>.

Thanks!
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.


However, all of these variables should collapse, as they do in the
earlier functions.
They also collapse on my machine on this testcase (which admittedly
has different code there).
It is, in fact, *incredibly* strange that not a single variable is
collapsed or unified in this function.

I'm not sure what to do here.
Can you poke around in perform_var_substitution and see if you can
figure out what conditions are causing all the variables to fail out
of the collapsing.  Particularly, roughly every variable that has a
constaint like foo = ESCAPED_VARS in the dump should be getting
collapsed to ESCAPED_VARS.


Can you poke


-- 


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


  parent reply	other threads:[~2006-11-05 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 23:07 [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   ` Daniel Berlin
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   ` Daniel Berlin
2006-11-05 21:48 ` dberlin at dberlin dot org [this message]
2006-11-06  0:43 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-07 17:40 ` dberlin at dberlin dot org
2006-11-09 17:24   ` Daniel Berlin
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:07 ` 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=20061105214810.28911.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).