public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "myway dot cn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34882] g++: Internal error: Killed (program cc1plus)
Date: Sat, 02 Feb 2008 12:06:00 -0000 [thread overview]
Message-ID: <20080202120601.19252.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34882-15669@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from myway dot cn at gmail dot com 2008-02-02 12:06 -------
(In reply to comment #6)
> The initialize_command_download() exposes the usual memory-hungriness of GCC
> with repetitive C++ initializers. We have plenty of bugreports with testcases
> for this, closing as invalid. And yes, 32MB + 200MB swap will never make
> you happy with C++ and gcc.
>
However, it's not the 1st time that i compiled rtorrent on NSLU2 Debian etch
platform.
Therefore, why this gcc version 4.2.3 cause this issues?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34882
prev parent reply other threads:[~2008-02-02 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 7:54 [Bug c++/34882] New: " myway dot cn at gmail dot com
2008-01-20 13:39 ` [Bug middle-end/34882] " pinskia at gcc dot gnu dot org
2008-01-23 10:44 ` myway dot cn at gmail dot com
2008-01-23 10:48 ` myway dot cn at gmail dot com
2008-01-26 13:43 ` pinskia at gcc dot gnu dot org
2008-01-27 0:14 ` tbm at cyrius dot com
2008-01-27 13:35 ` rguenth at gcc dot gnu dot org
2008-02-02 12:06 ` myway dot cn at gmail dot com [this message]
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=20080202120601.19252.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).