public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debora dot j dot estey at lmco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14179] New: out of memory
Date: Tue, 17 Feb 2004 17:10:00 -0000	[thread overview]
Message-ID: <20040217171044.14179.debora.j.estey@lmco.com> (raw)

We are trying to move from gcc 2.95 to 3.3.1. We are using cygwin and the code 
that will not compile is code in a library generated by another group. we must 
use it as is. The other group also uses the library but they use a greenhills 
compiler. The code will compile with gcc 2.95 but gcc 3.3.1 give us this error: 

cc1plus: out of memory allocating 65536 bytes after a total of 402620416 bytes

The gcc -v produces this information : 
Reading specs from /bin/../lib/gcc-lib/i686-pc-cygwin/3.3.1/specs
Configured with: /netrel/src/gcc-3.3.1-2/configure --enable-
languages=c,c++,f77,java --enable-libgcj --enable-threads=posix --with-system-
zlib --enable-nls --without-included-gettext --enable-interpreter --enable-sjlj-
exceptions --disable-version-specific-runtime-libs --enable-shared --build=i686-
pc-linux --host=i686-pc-cygwin --target=i686-pc-cygwin --prefix=/usr --exec-
prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --
includedir=/nonexistent/include --libexecdir=/usr/sbin
Thread model: posix
gcc version 3.3.1 (cygming special)

-- 
           Summary: out of memory
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P1
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: debora dot j dot estey at lmco dot com
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-02-17 17:10 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 17:10 debora dot j dot estey at lmco dot com [this message]
2004-02-17 17:15 ` [Bug c++/14179] " debora dot j dot estey at lmco dot com
2004-02-17 17:25 ` debora dot j dot estey at lmco dot com
2004-02-17 17:52 ` giovannibajo at libero dot it
2004-02-17 18:00 ` [Bug c++/14179] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-02-17 18:10 ` pinskia at gcc dot gnu dot org
2004-03-08 23:08 ` mmitchel at gcc dot gnu dot org
2004-06-07  3:25 ` pinskia at gcc dot gnu dot org
2004-09-15 14:27 ` [Bug c++/14179] [3.3/3.4/4.0 " giovannibajo at libero dot it
2004-09-15 16:30 ` mark at codesourcery dot com
2004-09-17 18:50 ` giovannibajo at libero dot it
2004-09-18 13:10 ` giovannibajo at libero dot it
2004-09-20 23:05 ` cvs-commit at gcc dot gnu dot org
2004-09-21 21:12 ` cvs-commit at gcc dot gnu dot org
2004-09-21 22:50 ` cvs-commit at gcc dot gnu dot org
2004-09-21 23:46 ` cvs-commit at gcc dot gnu dot org
2004-09-22  0:36 ` giovannibajo at libero dot it
2004-09-22  0:38 ` giovannibajo at libero dot it
2004-09-22  0:43 ` giovannibajo at libero dot it
2004-09-22  0:54 ` mark at codesourcery dot com
2004-09-22 13:51 ` bonzini at gnu dot org
2004-09-22 15:33 ` mark at codesourcery dot com
2004-09-22 15:39 ` mmitchel at gcc dot gnu dot org
2004-09-22 15:43 ` paolo dot bonzini at polimi dot it
2004-09-22 15:54 ` mark at codesourcery dot com
2004-09-22 15:56 ` paolo dot bonzini at polimi dot it
2004-09-23  0:02 ` giovannibajo at libero dot it
2004-09-23  0:16 ` mark at codesourcery dot com
2004-09-23  1:00 ` giovannibajo at libero dot it
2004-09-23  1:37 ` mark at codesourcery dot com
2004-09-24 16:02 ` bonzini at gcc dot gnu dot org
2004-09-24 16:06 ` bonzini at gcc dot gnu dot org
2004-09-24 16:53 ` mark at codesourcery dot com
2004-09-24 18:53 ` bonzini at gnu dot org
2004-09-24 18:54 ` [Bug c++/14179] array parsing could be made faster bonzini at gcc dot gnu dot org
2004-09-25  0:50 ` [Bug c++/14179] [3.3/3.4/4.0 Regression] " giovannibajo at libero dot it
2004-10-26 16:11 ` [Bug c++/14179] [3.3/3.4/4.0 Regression] out of memory while parsing array with many initializers debora dot j dot estey at lmco dot com
2004-10-26 16:14 ` pinskia at gcc dot gnu dot org
2004-10-27 15:43 ` giovannibajo at libero dot it
2004-12-23 12:35 ` steven at gcc dot gnu dot org
2004-12-24  2:23 ` giovannibajo at libero dot it
2004-12-24  7:07 ` steven at gcc dot gnu dot org
2005-04-21  5:03 ` [Bug c++/14179] [3.3/3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-05-03 22:44 ` debora dot j dot estey at lmco dot com
2005-07-08  1:43 ` [Bug c++/14179] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-25  1:39 ` pinskia at gcc dot gnu dot org
2005-09-27 16:14 ` mmitchel 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=20040217171044.14179.debora.j.estey@lmco.com \
    --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).