From 79ec127b7f4ab6827836b679aa6ecf0474091b5a Mon Sep 17 00:00:00 2001
From: Benjamin Kosnik [20.4.1.1]/6
- Complete details cam be found in the C++ standard, look in
+ Complete details can be found in the C++ standard, look in
[20.4 Memory]
.
The easiest way of fulfilling the requirements is to call
@@ -93,9 +93,9 @@
or loading and unloading shared objects in memory. As such, using
caching allocators on systems that do not support
abi::__cxa_atexit
is not recommended.
-
The only allocator interface that - is support is the standard C++ interface. As such, all STL + is supported is the standard C++ interface. As such, all STL containers have been adjusted, and all external allocators have been modified to support this change.
@@ -106,7 +106,7 @@
The base class that allocator
is derived from
may not be user-configurable.
-
It's difficult to pick an allocation strategy that will provide maximum utility, without excessively penalizing some behavior. In fact, it's difficult just deciding which typical actions to measure @@ -127,7 +127,7 @@ Insertion and erasure in a multi-threaded environment.
This test shows the ability of the allocator to reclaim memory
- on a pre-thread basis, as well as measuring thread contention
+ on a per-thread basis, as well as measuring thread contention
for memory resources.
Test source
here.
@@ -143,7 +143,7 @@
The current default choice for
allocator
is
__gnu_cxx::new_allocator
.
-
In use, allocator
may allocate and
deallocate using implementation-specified strategies and
heuristics. Because of this, every call to an allocator object's
@@ -285,8 +285,8 @@
The thr
boolean determines whether the
pool should be manipulated atomically or not. When
thr
= true
, the allocator
- is is thread-safe, while thr
=
- false
, and is slightly faster but unsafe for
+ is thread-safe, while thr
=
+ false
, is slightly faster but unsafe for
multiple threads.
For thread-enabled configurations, the pool is locked with a @@ -308,11 +308,11 @@ A high-performance allocator that uses a bit-map to keep track of the used and unused memory locations. It has its own documentation, found here. -