From 1cb1de7ead03894075ea7392879654d3d968f044 Mon Sep 17 00:00:00 2001 From: Phil Edwards Date: Mon, 28 Jul 2003 04:13:58 +0000 Subject: user.cfg.in, [...]: Change GLIBCPP to GLIBCXX (and explain as needed). 2003-07-28 Phil Edwards * docs/doxygen/user.cfg.in, docs/html/abi.txt, docs/html/debug.html, docs/html/test.html, docs/html/17_intro/headers_cc.txt, docs/html/17_intro/howto.html, docs/html/ext/howto.html: Change GLIBCPP to GLIBCXX (and explain as needed). From-SVN: r69879 --- libstdc++-v3/docs/html/debug.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'libstdc++-v3/docs/html/debug.html') diff --git a/libstdc++-v3/docs/html/debug.html b/libstdc++-v3/docs/html/debug.html index 0ca332c..dcd035c 100644 --- a/libstdc++-v3/docs/html/debug.html +++ b/libstdc++-v3/docs/html/debug.html @@ -105,7 +105,7 @@ there are different kinds of allocation schemes that can be used by std::allocator . For implementation details, see this document and look specifically for - GLIBCPP_FORCE_NEW. + GLIBCXX_FORCE_NEW.

In a nutshell, the default allocator used by @@ -120,7 +120,7 @@ C++ tools: the first that can do this is valgrind 1.0.4, but later versions should work at least as well. Second of all, use a completely unoptimized build to avoid confusing valgrind. Third, - use GLIBCPP_FORCE_NEW to keep extraneous pool allocation noise from + use GLIBCXX_FORCE_NEW to keep extraneous pool allocation noise from cluttering debug information.

-- cgit v1.1