-
The namespace UID allocators depend on direct access to etcd (for their allocation map) and aren't structured like a classic controller.
While allocation *should* happen on creation (i.e. making it…
-
```
No instructions or dependency info. $./build.sh craps out with
In file included from jni/../jni/stlport/stlport/stl/_alloc.h:62:0,
from jni/../jni/stlport/stlport/memory:32,
from jni/../jni/stlpo…
-
```
No instructions or dependency info. $./build.sh craps out with
In file included from jni/../jni/stlport/stlport/stl/_alloc.h:62:0,
from jni/../jni/stlport/stlport/memory:32,
from jni/../jni/stlpo…
-
```
No instructions or dependency info. $./build.sh craps out with
In file included from jni/../jni/stlport/stlport/stl/_alloc.h:62:0,
from jni/../jni/stlport/stlport/memory:32,
from jni/../jni/stlpo…
-
`cuda::mr` is intended to be the future of heterogenous memory allocation in CUDA C++. It is inspired heavily by lessons learned in RMM and our experience with the `device_memory_resource*` and friend…
-
Seemed like a good idea at the time, is not anymore. Use Teeworlds' array instead and ring buffers/allocators where applicable.
-
...as soon as it actually gets included in Phobos, that is.
-
```
No instructions or dependency info. $./build.sh craps out with
In file included from jni/../jni/stlport/stlport/stl/_alloc.h:62:0,
from jni/../jni/stlport/stlport/memory:32,
from jni/../jni/stlpo…
-
-
Feature gate: `#![feature(kernel_allocation_new)]`
This is a tracking issue for functions associated with runtime creation of arbitrary memory allocators.
Due to the memory allocator bootstrap p…