public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/28871] massive C++ compile time slowdown
Date: Mon, 04 Sep 2006 15:25:00 -0000 [thread overview]
Message-ID: <20060904152543.15331.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28871-365@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from bkoz at gcc dot gnu dot org 2006-09-04 15:25 -------
...this is a PCH vs. anonymous namespace issue. Crack smoking! If PCH is
incommpatible with anonymous namespaces, then -Winvalid-pch needs to warn about
it at the time of pch creation.
I'm going to check in a fix to this, in that I'm going to revert to using
stdc++.h and remove the one use of anonymous namespaces.
I'll also make an enhancement request about -Winvalid-pch vs. anonymous
namespaces.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28871
next prev parent reply other threads:[~2006-09-04 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 12:42 [Bug c++/28871] New: " bkoz at gcc dot gnu dot org
2006-08-28 13:24 ` [Bug c++/28871] " pinskia at gcc dot gnu dot org
2006-08-29 10:36 ` bkoz at gcc dot gnu dot org
2006-08-29 10:44 ` bkoz at gcc dot gnu dot org
2006-09-04 15:25 ` bkoz at gcc dot gnu dot org [this message]
2006-09-04 15:26 ` bkoz at gcc dot gnu dot org
2006-09-04 15:41 ` bkoz 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=20060904152543.15331.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).