public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36391] Compilation never ends
Date: Wed, 22 Oct 2008 17:07:00 -0000 [thread overview]
Message-ID: <20081022170548.16984.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36391-16263@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from manu at gcc dot gnu dot org 2008-10-22 17:05 -------
(In reply to comment #7)
>
> testcase compiles on recent 4.3 with -m{32,64} -O{0..3} w/ boost-1.36.0.
> it needs ~1second/~120MB on my quad core box.
>
Thanks Pawel! If you could test also a recent GCC 4.4 that would be perfect.
Anyway, this seems FIXED. Please reopen if you can reproduce the problem with a
recent GCC release (or trunk).
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36391
next prev parent reply other threads:[~2008-10-22 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 14:06 [Bug c++/36391] New: " ivan at cvut dot cz
2008-05-30 14:10 ` [Bug c++/36391] " ivan at cvut dot cz
2008-06-05 14:36 ` ivan at cvut dot cz
2008-06-15 16:06 ` ivan at cvut dot cz
2008-06-15 16:12 ` ivan at cvut dot cz
2008-09-11 7:50 ` rhorstmann at securecomputing dot com
2008-10-21 21:26 ` manu at gcc dot gnu dot org
2008-10-22 16:59 ` pluto at agmk dot net
2008-10-22 17:07 ` manu at gcc dot gnu dot org [this message]
2008-10-23 7:58 ` ivan at vc dot cvut dot cz
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=20081022170548.16984.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).