public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org To: bjornw@planetarion.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: libstdc++/4219: stl_alloc using -D__USE_MALLOC fails Date: Tue, 04 Sep 2001 14:02:00 -0000 [thread overview] Message-ID: <20010904210227.14416.qmail@sourceware.cygnus.com> (raw) Synopsis: stl_alloc using -D__USE_MALLOC fails Responsible-Changed-From-To: unassigned->ljrittle Responsible-Changed-By: ljrittle Responsible-Changed-When: Tue Sep 4 14:02:27 2001 Responsible-Changed-Why: Look like mine. State-Changed-From-To: open->feedback State-Changed-By: ljrittle State-Changed-When: Tue Sep 4 14:02:27 2001 State-Changed-Why: BTW, I think it would be a good idea to make the change you spotted. Is there a reason why you can't follow this advice on the new way to use the malloc interface in your application (from ./include/bits/c++config but see the primary documentation on the matter as well): // Default to the typically high-speed, pool-based allocator (as // libstdc++-v2) instead of the malloc-based allocator (libstdc++-v3 // snapshots). See libstdc++-v3/docs/html/17_intro/howto.html for // details on why you don't want to override this setting. Ensure // that threads are properly configured on your platform before // assigning blame to the STL container-memory allocator. After doing // so, please report any possible issues to libstdc++@gcc.gnu.org . // Do not blindly #define __USE_MALLOC here or on the command line. The problem with users defining __USE_MALLOC on the command line is that it is a subtle ABI change that may cause you problems... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4219&database=gcc
next reply other threads:[~2001-09-04 14:02 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-04 14:02 ljrittle [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-03 18:56 ljrittle 2001-11-03 15:49 ljrittle 2001-09-04 1:46 bjornw
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=20010904210227.14416.qmail@sourceware.cygnus.com \ --to=ljrittle@gcc.gnu.org \ --cc=bjornw@planetarion.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).