-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal memory allocation callbacks #25
Comments
The Vulkan backend is still in an experimental state. Compared to the D3D12 and Metal backends more usable, though. |
What about memory control of the internal structures that LLGL itself allocates? Is there a way for us to define allocation routines for the library as a whole? |
There are currently no interfaces or plans for this fine-grained memory control. LLGL uses the default STL containers and allocators only (with very few exceptions). |
I guess an alternative then is to overload the default new and delete. I've got allocation tracking for leak detection and a few cache coherence tricks I'm using to squeeze some perf out of my framework. |
This ticket got stale. There feature doesn't have priority so I will close this as Won't Fix. |
Does LLGL have support for host memory allocations callbacks ? Such as VkAllocationCallbacks for vulkan? How about other apis (dx, ogl, etc) and other library allocations ?
If not, is this planned ?
The text was updated successfully, but these errors were encountered: