This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/17315] Strange compile-time regression in cpp against gcc3.4.1
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Sep 2004 11:38:41 -0000
- Subject: [Bug libstdc++/17315] Strange compile-time regression in cpp against gcc3.4.1
- References: <20040904072757.17315.kgardas@objectsecurity.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pcarlini at suse dot de 2004-09-08 11:38 -------
Yes, Giovanni, I agree that this kind of test is worth doing. Just passing
--enable-libstdcxx-allocator=new at configure time suffices. The viceversa
would be also useful, that is, passing --enable-libstdcxx-allocator=mt to
3.4.1 configure. However, again, please remember that the user, in general, is
*not* supposed to preprocess with 3.4.1 and compile/link with 3.5.0 (or much
more generally, use an allocator type at pre-processing time and a different
one at compile/link time), *very* bad things can happen... ;)
Also, please consider that mt_allocator is more complex and *is* expected to
be more challenging for the compiler: its performance are *much* better, no
free lunch... ;)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17315