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 middle-end/41043] [4.4/4.5 Regression] virtual memory exhausted: Cannot allocate memory
Date: Tue, 16 Feb 2010 13:18:00 -0000	[thread overview]
Message-ID: <20100216131744.7958.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41043-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rguenth at gcc dot gnu dot org  2010-02-16 13:17 -------
#define FOO ((long)i * (long)i)
#define FOO2 (FOO * FOO)
#define FOO3 (FOO2 * FOO2)
#define FOO4 (FOO3 * FOO3)
#define FOO5 (FOO4 * FOO4)
#define FOO6 (FOO5 * FOO5)
#define FOO7 (FOO6 * FOO6)
#define FOO8 (FOO7 * FOO7)
#define FOO9 (FOO8 * FOO8)
#define FOO10 (FOO9 * FOO9)
#define FOO11 (FOO10 * FOO10)
#define FOO12 (FOO11 * FOO11)
#define FOO13 (FOO12 * FOO12)
#define FOO14 (FOO13 * FOO13)
#define FOO15 (FOO14 * FOO14)
#define FOO16 (FOO15 * FOO15)
int foo (int i)
{
  return (int)(FOO14);
}

At -O0:

FOO12: 1.6s
FOO13: 3.2s
FOO14: 6.7s
FOO15: 13s

we just take endless time with the above, memory usage isn't as bad as
with VRP.


-- 


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


  parent reply	other threads:[~2010-02-16 13:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 12:29 [Bug fortran/41043] New: " dominiq at lps dot ens dot fr
2009-08-12 13:14 ` [Bug fortran/41043] " rguenth at gcc dot gnu dot org
2009-08-12 13:36 ` rguenth at gcc dot gnu dot org
2009-08-12 13:37 ` rguenth at gcc dot gnu dot org
2009-08-24  1:05 ` mmitchel at gcc dot gnu dot org
2009-10-15 12:58 ` [Bug middle-end/41043] " jakub at gcc dot gnu dot org
2010-01-02 21:02 ` fxcoudert at gcc dot gnu dot org
2010-02-16 10:27 ` rguenth at gcc dot gnu dot org
2010-02-16 13:00 ` rguenth at gcc dot gnu dot org
2010-02-16 13:18 ` rguenth at gcc dot gnu dot org [this message]
2010-02-16 13:22 ` dominiq at lps dot ens dot fr
2010-02-16 15:06 ` rguenth at gcc dot gnu dot org
2010-02-16 16:12 ` rguenth at gcc dot gnu dot org
2010-02-16 16:12 ` [Bug middle-end/41043] [4.4 " rguenth at gcc dot gnu dot org
2010-02-16 17:06 ` dominiq at lps dot ens dot fr
2010-02-17  9:40 ` rguenth at gcc dot gnu dot org
2010-02-21 12:49 ` dominiq at lps dot ens dot fr
2010-02-21 12:50 ` rguenther at suse dot de
2010-04-08  9:23 ` rguenth at gcc dot gnu dot org
2010-04-30  9:01 ` jakub 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=20100216131744.7958.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).