This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/33633] [4.3 Regression] -D_GLIBCXX_DEBUG vs ext/hash_*
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Oct 2007 09:19:15 -0000
- Subject: [Bug libstdc++/33633] [4.3 Regression] -D_GLIBCXX_DEBUG vs ext/hash_*
- References: <bug-33633-133@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from pcarlini at suse dot de 2007-10-10 09:19 -------
(In reply to comment #2)
> Here's my plan for the legacy hash containers:
>
> 1) port debug mode to tr1 associative containers
> 2) move ext/hash containers to deprecated
>
> Thoughts?
Certainly, I agree with the (mid term?) plan!
> Anyway.
>
> This issue is a macro name mix-up. Here's I'll check in the attached fix
> shortly.
... short term, however, seems a good idea manage to keep the ext facilities
working (well, our own testsuite infrastructure still uses the hash_*
containers and adding -D_GLIBCXX_DEBUG to the testing switches broke testing
completely, that's how I actually noticed ;)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33633