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 tree-optimization/27004] [4.1/4.2 Regression] Insane amount of memory needed at -O1 and above because of salias
Date: Mon, 03 Apr 2006 14:37:00 -0000 [thread overview]
Message-ID: <20060403143752.25525.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27004-7849@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from dberlin at gcc dot gnu dot org 2006-04-03 14:37 -------
Subject: Re: New: [4.1/4.2 Regression]
Insane amount of memory needed at -O1 and above because of salias
On Mon, 2006-04-03 at 13:43 +0000, bonzini at gnu dot org wrote:
> spinning a separate bug from PR26830. we are creating a lot of field memory
> tags, each of which is present in a 900-argument phi, which causes us to use
> more memory than 4.0.
>
> to some extent this is unavoidable, but I wonder if we could throttle things
> down a bit?
>
Err, why do we have a 900 argument phi?
Seems a bit large.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27004
next prev parent reply other threads:[~2006-04-03 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 13:43 [Bug tree-optimization/27004] New: " bonzini at gnu dot org
2006-04-03 14:37 ` dberlin at dberlin dot org [this message]
2006-04-03 14:39 ` [Bug tree-optimization/27004] " rguenther at suse dot de
2006-04-05 18:33 ` [Bug tree-optimization/27004] [4.1/4.2 Regression] Insane amount of memory needed at -O1 and above because of salias and large switch pinskia at gcc dot gnu dot org
2006-04-16 19:16 ` mmitchel at gcc dot gnu dot org
2006-05-25 2:39 ` mmitchel at gcc dot gnu dot org
2007-02-14 9:10 ` [Bug tree-optimization/27004] [4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-11-04 12:47 ` rguenth at gcc dot gnu dot org
2007-11-04 13:34 ` rguenth at gcc dot gnu dot org
2007-11-04 13:38 ` rguenth at gcc dot gnu dot org
2008-07-04 20:24 ` [Bug tree-optimization/27004] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-12-08 14:43 ` jakub at gcc dot gnu dot org
2008-12-08 14:49 ` [Bug tree-optimization/27004] [4.2/4.3 " rguenth at gcc dot gnu dot org
2009-03-31 19:33 ` [Bug tree-optimization/27004] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:34 ` rguenth at gcc dot gnu dot org
2010-04-20 13:23 ` 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=20060403143752.25525.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).