public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "livubuntu at lalescu dot ro" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/37008] [4.2 Regression] OOM on a big c++ file
Date: Sun, 03 Aug 2008 07:24:00 -0000	[thread overview]
Message-ID: <20080803072327.7147.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37008-16551@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from livubuntu at lalescu dot ro  2008-08-03 07:23 -------
(In reply to comment #4)
> (In reply to comment #2)
> > g++: Internal error: Killed (program cc1plus)
> > 
> > this means your system ran out of memory and the operating system decided
> > to kill the compiler.  Note that memory usage problems are unlikely to be
> > fixed in a further release of GCC 4.2, but you might want to try GCC 4.3.1
> > or later which uses less memory than GCC 4.1 for your testcase.
> > 
> 
> I tried the GCC 4.3.1, of course, but I got very very many weird warnings for
> the Qt included files. I tried the binary GCC 4.3.1 from Debian.
> 
> A collaborator reports that he compiled successfully FET for the same Qt as
> mine, with GCC 4.3.1, but for 32 bit version. He obtained only a few warnings.
> 
> Thank you for fast reply. I'll do some more tests with GCC 4.3.1 and maybe
> report bugs to Trolltech for Qt or report bugs here for GCC 4.3.1.
> 

I installed latest qt and gcc 4.3.1. Everything is fine, FET compiles OK, thank
you. It is very good that I get a few warnings which did not show up in gcc
4.1.3, and I saw a few mistakes of mine.


-- 


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


  parent reply	other threads:[~2008-08-03  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02  7:27 [Bug c++/37008] New: Crash bug " livubuntu at lalescu dot ro
2008-08-02  7:31 ` [Bug c++/37008] " livubuntu at lalescu dot ro
2008-08-02 11:48 ` rguenth at gcc dot gnu dot org
2008-08-02 11:49 ` rguenth at gcc dot gnu dot org
2008-08-02 11:50 ` [Bug c++/37008] [4.2 Regression] OOM " rguenth at gcc dot gnu dot org
2008-08-02 12:22 ` livubuntu at lalescu dot ro
2008-08-03  7:24 ` livubuntu at lalescu dot ro [this message]
2009-03-31 15:47 ` jsm28 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=20080803072327.7147.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).