This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
MT allocator, part 2...
- From: Stefan Olsson <stefan at noname4us dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Sat, 01 Jun 2002 13:27:32 +0200
- Subject: MT allocator, part 2...
- Organization: Noname4us
Hi again!
I forgot two other questions that has been on my mind for a while...
- operator new() always uses malloc() in libstdc++. Snip from the C++
standard 18.4.1.1 "Whether the attempt involves a call to the Standard C
library function malloc is unspecified." Have there been discussions
about using the default (or any other allocator such as the MT allocator
that I am talking about) instead? And if so, how could this be defined
without breaking the standard compliance?
- Basically the same question goes for allocation related to exception
handling (see function __cxa_allocate_exception(std::size_t thrown_size)
in libstdc++-v3/libsupc++/eh_alloc.cc). I fully understand that this is
a much more complex issue to solve, but exception handling is one of the
great features of C++ and if we can find a way to lower the performance
penalty of using it...
Brgds
/Stefan
--
In any organization there will always be one person who knows what is going on.
This person must be fired.