public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "grayyoga at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29433] using boost::MPL requires lots of memory
Date: Fri, 13 Oct 2006 12:21:00 -0000 [thread overview]
Message-ID: <20061013122057.30343.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29433-12712@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from grayyoga at gmail dot com 2006-10-13 12:20 -------
Subject: Re: using boost::MPL requires lots of memory
Ok, if there is anything else I could help, please mail me.
On 13 Oct 2006 12:18:51 -0000, rguenth at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #14 from rguenth at gcc dot gnu dot org 2006-10-13 12:18 -------
> Sure, but the crash is due to gcc running out of memory. And the third
> testcase is a good one to attack memory usage and compile-time problems on all
> of the three testcases.
>
> But don't hold your breath...
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29433
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29433
next prev parent reply other threads:[~2006-10-13 12:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 19:05 [Bug c++/29433] New: Internal error while compiling code using boost::MPL grayyoga at gmail dot com
2006-10-11 19:10 ` [Bug c++/29433] " grayyoga at gmail dot com
2006-10-11 19:13 ` grayyoga at gmail dot com
2006-10-11 19:14 ` grayyoga at gmail dot com
2006-10-11 19:36 ` pinskia at gcc dot gnu dot org
2006-10-11 21:56 ` [Bug c++/29433] using boost::MPL requires lots of memory rguenth at gcc dot gnu dot org
2006-10-12 8:20 ` rguenth at gcc dot gnu dot org
2006-10-12 9:52 ` grayyoga at gmail dot com
2006-10-12 13:09 ` rguenth at gcc dot gnu dot org
2006-10-12 16:50 ` grayyoga at gmail dot com
2006-10-12 19:56 ` grayyoga at gmail dot com
2006-10-13 10:58 ` rguenth at gcc dot gnu dot org
2006-10-13 11:05 ` rguenth at gcc dot gnu dot org
2006-10-13 12:16 ` grayyoga at gmail dot com
2006-10-13 12:19 ` rguenth at gcc dot gnu dot org
2006-10-13 12:21 ` grayyoga at gmail dot com [this message]
2006-10-13 13:19 ` rguenth at gcc dot gnu dot org
2006-11-22 12:39 ` rguenth at gcc dot gnu dot org
2006-11-28 12:38 ` rguenth at gcc dot gnu dot org
2006-11-28 16:21 ` patchapp at dberlin dot org
2006-11-30 16:15 ` patchapp at dberlin dot org
2006-12-01 16:38 ` rguenth at gcc dot gnu dot org
2006-12-01 16:38 ` rguenth at gcc dot gnu dot org
2007-02-23 14:21 ` rguenth at gcc dot gnu dot org
2007-06-12 11:30 ` rguenth 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=20061013122057.30343.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).