public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lucier at math dot purdue dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12655] New: Excessive memory usage---32-bit virtual memory exhausted
Date: Fri, 17 Oct 2003 03:28:00 -0000	[thread overview]
Message-ID: <20031017032825.12655.lucier@math.purdue.edu> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: Excessive memory usage---32-bit virtual memory exhausted
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: lucier at math dot purdue dot edu
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: sparc-sun-solaris2.8
  GCC host triplet: sparc-sun-solaris2.8
GCC target triplet: sparc-sun-solaris2.8

With this compiler

banach-19% gcc -v
Reading specs from
/export/mdd0/users/lucier/local/gcc-ssa/bin/../lib/gcc/sparc-sun-solaris2.8/3.5-tree-ssa/specs
Configured with: ../configure --enable-checking=no --enable-languages=c
--prefix=/home/c/lucier/local/gcc-ssa
Thread model: posix
gcc version 3.5-tree-ssa 20031016 (merged 20031005)

I get the following results on the file

http://www.math.purdue.edu/~lucier/bugzilla/1/_num.i.gz

when it exhausts the 2GB (?) virtual memory process size after about 90 minutes
(?) of cpu time.

gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2
-fno-trapping-math -fno-strict-aliasing -fomit-frame-pointer -fPIC -fno-common
-save-temps -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY
-D___GAMBCDIR=\"/usr/local/\" -c _num.c
virtual memory exhausted: Not enough space
make[1]: *** [_num.o] Error 1


             reply	other threads:[~2003-10-17  3:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  3:28 lucier at math dot purdue dot edu [this message]
2003-10-17 14:14 ` [Bug optimization/12655] " pinskia at gcc dot gnu dot org
2003-10-17 14:20 ` [Bug optimization/12655] [tree-ssa] " pinskia at gcc dot gnu dot org
2003-11-14  7:15 ` steven at gcc dot gnu dot org
2003-11-18  6:01 ` pinskia at gcc dot gnu dot org
2003-11-18 15:45 ` amacleod at redhat dot com
2003-11-18 16:49 ` pinskia at gcc dot gnu dot org
2003-11-19  5:30 ` lucier at math dot purdue dot edu
2003-11-19  5:33 ` pinskia 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=20031017032825.12655.lucier@math.purdue.edu \
    --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).